<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti/src/arti-example-config.toml, branch arti-v1.8.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-11-25T15:44:46Z</updated>
<entry>
<title>Merge branch 'intro-dos' into 'main'</title>
<updated>2025-11-25T15:44:46Z</updated>
<author>
<name>gabi-250</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-11-25T15:44:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c0969cea4fce1ae3f7f148add28ce479a317febf'/>
<id>urn:sha1:c0969cea4fce1ae3f7f148add28ce479a317febf</id>
<content type='text'>
arti: Add rate_limit_at_intro to the example config

See merge request tpo/core/arti!3493</content>
</entry>
<entry>
<title>arti: Clarify that the "burst" is not per second.</title>
<updated>2025-11-25T15:03:48Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-11-25T15:03:48Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4617a60771ab6d7df8cd81ea27f188efec585e45'/>
<id>urn:sha1:4617a60771ab6d7df8cd81ea27f188efec585e45</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arti: Add rate_limit_at_intro to the example config</title>
<updated>2025-11-25T14:44:21Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-11-25T14:17:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e21fcb0199c0f8ce942583117c67b1f8bf7b9699'/>
<id>urn:sha1:e21fcb0199c0f8ce942583117c67b1f8bf7b9699</id>
<content type='text'>
This is mostly c&amp;p from the `rate_limit_at_intro` docs, I just added an
extra paragraph to clarify the meaning of the tuple elements (i.e.
`(rate, burst)`).
</content>
</entry>
<entry>
<title>hsservice: Clarify what max_concurrent_streams_per_circuit does</title>
<updated>2025-11-25T13:39:44Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-11-25T13:37:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1186228c0d7ef7786d2828dbc0eda5ff19dafa12'/>
<id>urn:sha1:1186228c0d7ef7786d2828dbc0eda5ff19dafa12</id>
<content type='text'>
At first glance, this might seem equivalent to C Tor's
`HiddenServiceMaxStreams` option, but it's actually
`HiddenServiceMaxStreamsCloseCircuit` (Arti doesn't implement the
former).
</content>
</entry>
<entry>
<title>Merge branch 'prop368-v4' into 'main'</title>
<updated>2025-11-13T15:47:31Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-11-13T15:47:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f7ed6c26a36ed2cd0b2c5e76454213293aaeeb2f'/>
<id>urn:sha1:f7ed6c26a36ed2cd0b2c5e76454213293aaeeb2f</id>
<content type='text'>
Implement a usage-based timeout for strongly isolated circuits (prop368)

Closes #2237

See merge request tpo/core/arti!3430</content>
</entry>
<entry>
<title>Merge branch 'disable-hidden-service' into 'main'</title>
<updated>2025-11-12T16:08:04Z</updated>
<author>
<name>wesleyac</name>
<email>wesleyac@torproject.org</email>
</author>
<published>2025-11-12T16:08:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9ca5882dc9ac6b883bfe1579efa7359a4d67a8dc'/>
<id>urn:sha1:9ca5882dc9ac6b883bfe1579efa7359a4d67a8dc</id>
<content type='text'>
arti/arti-client/tor-hsservice: Support disabling onion services in the config

Closes #2133

See merge request tpo/core/arti!3253</content>
</entry>
<entry>
<title>circmgr: Add a timeout setting for long-lived circuits.</title>
<updated>2025-11-12T15:00:55Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-11-03T19:51:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4085cefe79415eff112e4b29c4c5bea345bbaf23'/>
<id>urn:sha1:4085cefe79415eff112e4b29c4c5bea345bbaf23</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arti: Experimental support for tokio-console</title>
<updated>2025-11-06T15:18:46Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-11-05T14:46:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4d5da95e49c5fb01f07542cfb6063aab694e7229'/>
<id>urn:sha1:4d5da95e49c5fb01f07542cfb6063aab694e7229</id>
<content type='text'>
This is controlled by a new option, `logging.tokio_console.enabled`.
It requires building with `--cfg tokio_unstable`.  See documentation
and comments for more information.
</content>
</entry>
<entry>
<title>arti/tor-hsservice: don't warn on autostart</title>
<updated>2025-10-16T22:48:46Z</updated>
<author>
<name>hashcatHitman</name>
<email>3924-hashcatHitman@gitlab.torproject.org</email>
</author>
<published>2025-10-03T07:27:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=47e00144051d73c5b54563ced2f443cf9eda9b16'/>
<id>urn:sha1:47e00144051d73c5b54563ced2f443cf9eda9b16</id>
<content type='text'>
The "enabled" config option is back to using a regular `bool`. When
unset, it defaults to true, and the service runs as if it had been set.

Signed-off-by: hashcatHitman &lt;3924-hashcatHitman@gitlab.torproject.org&gt;
</content>
</entry>
<entry>
<title>arti: fix hs "enabled" in example config</title>
<updated>2025-10-16T22:48:46Z</updated>
<author>
<name>hashcatHitman</name>
<email>3924-hashcatHitman@gitlab.torproject.org</email>
</author>
<published>2025-09-21T19:26:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bbc28791231ef7c47bfd77de60cd60075306cefb'/>
<id>urn:sha1:bbc28791231ef7c47bfd77de60cd60075306cefb</id>
<content type='text'>
I didn't realize we had tests that made use of the example config. The
pre-commit and pre-push hooks I had didn't trigger them, so my
modification to the example config silently got through and caused
`cfg::test::onion_services` to fail in CI.

The issue was that I had put my example for
`onion_services."allium-cepa".enabled` with a default of `true`. The
correct default is actually `"auto"`, so I switched it and improved the
description of the options.

I've fixed my hooks. Which, to be fair, are just the hooks provided in
`./maint/hooks/`. Maybe those should be improved?

Signed-off-by: hashcatHitman &lt;3924-hashcatHitman@gitlab.torproject.org&gt;
</content>
</entry>
</feed>
