<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-circmgr/src/config.rs, branch arti-v0.0.3</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.3</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.3'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2021-12-16T13:37:50Z</updated>
<entry>
<title>Adjust comment to be accurate wrt #263.</title>
<updated>2021-12-16T13:37:50Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-16T13:37:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a0870f8f7969eae49edc4e4b62376083bb34ab82'/>
<id>urn:sha1:a0870f8f7969eae49edc4e4b62376083bb34ab82</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Make preemptive circuits reconfigurable.</title>
<updated>2021-12-07T21:42:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-07T21:42:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0f8d6207578e6fabd8470df7745bfb7c342cf408'/>
<id>urn:sha1:0f8d6207578e6fabd8470df7745bfb7c342cf408</id>
<content type='text'>
This required re-centralizing the configuration object for preemptive
circuits, since previously the settings from it were a bit spread out
over the crate.
</content>
</entry>
<entry>
<title>Make circuit_timing reconfigurable.</title>
<updated>2021-12-07T21:08:52Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-07T21:08:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a406e8e449485e21f9df82c1414cce5cde6d8fa5'/>
<id>urn:sha1:a406e8e449485e21f9df82c1414cce5cde6d8fa5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Allow on-the-fly changing of path_rules</title>
<updated>2021-12-07T20:42:14Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-07T18:37:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=11210124dac0405b12d31f4f0a82b8d1d5a34f44'/>
<id>urn:sha1:11210124dac0405b12d31f4f0a82b8d1d5a34f44</id>
<content type='text'>
And now the complexity begins: when the user changes the path_rules,
they not only want new circuits to obey those rules: they want
_all new requests_ to be put onto circuits that obey those rules.

That means that when the path rules become more restrictive, we need
to retire all the circuits, and make sure that currently pending
circuits aren't used for any requests.

If it's any comfort, doing this was even more complicated in C tor. ;)
</content>
</entry>
<entry>
<title>Clarify names and docs for predictive circuits.</title>
<updated>2021-12-07T17:09:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-07T17:00:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=48f77a93c0f030a6060965d96142adaf78c62f44'/>
<id>urn:sha1:48f77a93c0f030a6060965d96142adaf78c62f44</id>
<content type='text'>
Also, use humantime_serde, rather than a number of seconds, to indicate
configuration time.
</content>
</entry>
<entry>
<title>Rename circuits_preemptive to preemptive_circuits</title>
<updated>2021-12-07T17:06:53Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-07T16:38:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c2e20a242a3041b08afbc17f0420809fab2efc5d'/>
<id>urn:sha1:c2e20a242a3041b08afbc17f0420809fab2efc5d</id>
<content type='text'>
This obeys a few conventions:
  * adjective before noun
  * config objects end with "config"
</content>
</entry>
<entry>
<title>Allow configurability on preemptive circuits</title>
<updated>2021-12-07T15:04:41Z</updated>
<author>
<name>Neel Chauhan</name>
<email>neel@neelc.org</email>
</author>
<published>2021-12-07T15:04:41Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0e9c2d274ef5a1f3a21579d43ced512f17656797'/>
<id>urn:sha1:0e9c2d274ef5a1f3a21579d43ced512f17656797</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Ensure that all config sections have deny_unknown_fields</title>
<updated>2021-11-25T14:39:11Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-11-24T14:30:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=17266305e24074f4f8678bfcc5ed3c617c48c725'/>
<id>urn:sha1:17266305e24074f4f8678bfcc5ed3c617c48c725</id>
<content type='text'>
When we deserialize a configuration, we should reject unknown variables
(except when we have an explicit reason to allow them).
</content>
</entry>
<entry>
<title>Fix a few typos.</title>
<updated>2021-11-24T23:12:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-11-24T22:31:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f55950ab8d86fec3c5fbe33650c4a7001f9812b3'/>
<id>urn:sha1:f55950ab8d86fec3c5fbe33650c4a7001f9812b3</id>
<content type='text'>
Also fix some commonwealth spellings that had slipped in.
</content>
</entry>
<entry>
<title>Implement meta-builder pattern for TorClientConfig</title>
<updated>2021-11-22T14:53:52Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-11-22T00:05:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=307ca9b4d052c60e8e496012005efe1df6b90724'/>
<id>urn:sha1:307ca9b4d052c60e8e496012005efe1df6b90724</id>
<content type='text'>
This should be ergonomic than having to construct every section of the
configuration separately.
</content>
</entry>
</feed>
