<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirmgr/src/config.rs, branch arti-v1.0.1</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.0.1</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.0.1'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-07-22T14:04:25Z</updated>
<entry>
<title>Rename DirSkewTolerance to DirTolerance</title>
<updated>2022-07-22T14:04:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-22T14:04:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=41104137b12159d734f1171c1705c4e00f5244cd'/>
<id>urn:sha1:41104137b12159d734f1171c1705c4e00f5244cd</id>
<content type='text'>
This name is more accurate because we aren't only dealing with
clock skew here: we're also trying to tolerate the case where the
authorities fail to reach consensus for a while.
</content>
</entry>
<entry>
<title>impl_standard_builder: Use for tor_dirmgr::DownloadScheduleConfig</title>
<updated>2022-06-16T14:27:00Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-06-16T13:50:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8b724d40f82f32caab0421a2335f60c661cc1850'/>
<id>urn:sha1:8b724d40f82f32caab0421a2335f60c661cc1850</id>
<content type='text'>
</content>
</entry>
<entry>
<title>impl_standard_builder: Use for tor_dirmgr::NetworkConfig</title>
<updated>2022-06-16T14:27:00Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-06-16T13:49:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2ab5c0861e2e3a6a7a30b3de7fef2f781ec8be52'/>
<id>urn:sha1:2ab5c0861e2e3a6a7a30b3de7fef2f781ec8be52</id>
<content type='text'>
</content>
</entry>
<entry>
<title>impl_standard_builder: Use for tor_dirmgr::DirSkewTolerance</title>
<updated>2022-06-16T14:27:00Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-06-16T13:46:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e32210a398d90f6214d1652c0d241b7c4b85fa3e'/>
<id>urn:sha1:e32210a398d90f6214d1652c0d241b7c4b85fa3e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add some missing `serde(default)` to uses of humantime_serde::option</title>
<updated>2022-06-16T10:08:16Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-06-16T10:07:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4c65e9994d4466f00cd46e0c5a45a1755d3b583c'/>
<id>urn:sha1:4c65e9994d4466f00cd46e0c5a45a1755d3b583c</id>
<content type='text'>
Without this, if the substructure is provided, these fields are
mandatory within it.
</content>
</entry>
<entry>
<title>tor-dirmgr: Fix DirSkewTolerance</title>
<updated>2022-05-30T15:00:45Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-27T15:44:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=017906cdc7c59f91d4b574d6f71b441c0e6c3869'/>
<id>urn:sha1:017906cdc7c59f91d4b574d6f71b441c0e6c3869</id>
<content type='text'>
This was upposed to be one day, I presume!

Also complete a truncated sentence in the docs.
</content>
</entry>
<entry>
<title>tor-dirmgr: update status reporting to consider skew tolerance</title>
<updated>2022-05-11T16:11:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-11T16:09:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=db8bdbf9245c65cac79178fae731d1569de872ee'/>
<id>urn:sha1:db8bdbf9245c65cac79178fae731d1569de872ee</id>
<content type='text'>
In our status reporting code, we consider an
expired-but-still-usable directory still bootstrapped, but not 100%
bootstrapped.
</content>
</entry>
<entry>
<title>Add DirSkewTolerance section to DirMgr configuration.</title>
<updated>2022-05-11T16:11:17Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-11T14:47:11Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7dec007d63aa28972249038e16959f26b42bcf87'/>
<id>urn:sha1:7dec007d63aa28972249038e16959f26b42bcf87</id>
<content type='text'>
This new section describes how much variance we accept when it comes
to expired and not-yet-valid directory documents.  (Currently, the
only ones where this matters for are consensus documents and
authority certificates.)  A document that is invalid by no more than
these tolerances is not _live_, but it can still be used.

These tolerances serve two purposes:

 * First, they allow clients to run with a little more clock skew
   than they would tolerate otherwise.
 * Second, they allow clients to survive the situation where the
   authorities are unable to reach a consensus for a day or two.

Compare with Tor's REASONABLY_LIVE_TIME and NETWORKSTATUS_ALLOW_SKEW
constants; also compare with proposal 212.

Closes #412.
</content>
</entry>
<entry>
<title>Update tor-dirmgr to use fs-mistrust.</title>
<updated>2022-05-09T18:40:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-03T17:08:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=20a85061b6c7c5a88b98497aabdf986cd6a462df'/>
<id>urn:sha1:20a85061b6c7c5a88b98497aabdf986cd6a462df</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config derive attrs: Make builders serde, and validated structs not</title>
<updated>2022-05-05T09:35:52Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-04T16:45:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d47e94b45993162fece0d1bdfa4d3da0407a4861'/>
<id>urn:sha1:d47e94b45993162fece0d1bdfa4d3da0407a4861</id>
<content type='text'>
 * Builders additionally derive: Debug, Serialize, Deserialize.

 * Validated structs no longer derive: Serialize, Deserialize
   and all related attributes deleted.

 * As a consequence, all the `#[serde(deny_unknown_fields)]`
   are gone.  That means that right now unknown fields are totally
   ignored.  This is good for compatibility but poor for useability.
   Doing something better here is arti#417, in progress.

 * As a consequence, delete tor_dirmgr::retry::default_parallelism.
   (The default value was already duplicated into a builder attr.)
</content>
</entry>
</feed>
