<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdir/src, branch arti-v0.0.4</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.4</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.4'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2021-12-28T20:15:40Z</updated>
<entry>
<title>extend lints to include 'clippy::all'</title>
<updated>2021-12-28T20:15:40Z</updated>
<author>
<name>Daniel Eades</name>
<email>danieleades@hotmail.com</email>
</author>
<published>2021-12-28T20:15:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=592642a9e6c1c03e525f8b452f4b97e6fd17ff9b'/>
<id>urn:sha1:592642a9e6c1c03e525f8b452f4b97e6fd17ff9b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'reconfigure' into 'main'</title>
<updated>2021-12-13T14:49:23Z</updated>
<author>
<name>eta</name>
<email>tor@eta.st</email>
</author>
<published>2021-12-13T14:49:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8040f7afb260dd2cb1b863aee897f238017a9564'/>
<id>urn:sha1:8040f7afb260dd2cb1b863aee897f238017a9564</id>
<content type='text'>
Make most arti-client fields reconfigurable.

See merge request tpo/core/arti!181</content>
</entry>
<entry>
<title>tor-netdir: Resolve an XXXX about type ugliness</title>
<updated>2021-12-08T17:32:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-08T17:21:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a25960b44c17e32102d553bf716a542c196882d3'/>
<id>urn:sha1:a25960b44c17e32102d553bf716a542c196882d3</id>
<content type='text'>
We had no function to infallibly convert BoundedInt32&lt;{0 or 1},H&gt;
into a u32, even though we could have.  Because of that, we were
treating weight_scale as an i32 when logically it's a u32 or a
NonZeroU32.

Moreover, it turns out we were using an incorrect minimum for the
bwweightscale param, which would in theory have allowed the
authorities to make us divide by zero.

This patch introduces the necessary From&lt;&gt; implementation and uses
it.  It corrects the binimum bwweightscale, and prevents a
division-by-zero issue in case weight_scale is zero.
</content>
</entry>
<entry>
<title>Remove a couple of spec-related XXXXs in tor-netdir.</title>
<updated>2021-12-08T16:12:33Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-08T16:12:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6f52b81ce80427d2c1cb006dca871b86cb992cdc'/>
<id>urn:sha1:6f52b81ce80427d2c1cb006dca871b86cb992cdc</id>
<content type='text'>
I've opened torspec!54 to fill in the missing parts of the spec
about these issues.
</content>
</entry>
<entry>
<title>Make override_net_params take effect sooner.</title>
<updated>2021-12-08T00:26:01Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-08T00:22:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=42ae8c7a2ad776cfdc54c9587a3381a8a3189740'/>
<id>urn:sha1:42ae8c7a2ad776cfdc54c9587a3381a8a3189740</id>
<content type='text'>
This is still not as soon as I'd like: a real change here will require
refactoring DirMgr::notify().
</content>
</entry>
<entry>
<title>Merge branch 'bug183a_redux' into 'main'</title>
<updated>2021-12-07T16:01:30Z</updated>
<author>
<name>eta</name>
<email>tor@eta.st</email>
</author>
<published>2021-12-07T16:01:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a3f2e32485219a6e7b6776a506997b6e1c193193'/>
<id>urn:sha1:a3f2e32485219a6e7b6776a506997b6e1c193193</id>
<content type='text'>
Squash, refactor, and test !139 (Don't use same family as exit when picking a guard)

Closes #183

See merge request tpo/core/arti!173</content>
</entry>
<entry>
<title>tor-netdir: Use reproducible RNG in tests.</title>
<updated>2021-12-06T20:11:03Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-06T20:06:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d33d7f7fdd4a2aacbbad71a74a9b10043771695a'/>
<id>urn:sha1:d33d7f7fdd4a2aacbbad71a74a9b10043771695a</id>
<content type='text'>
The rand crate's documentation says it's not okay to rely on StdRng
having reproducible output.  So instead, let's switch to ChaCha12Rng
instead (which is what StrRng currently uses).
</content>
</entry>
<entry>
<title>Tests for new family-related functions.</title>
<updated>2021-12-06T16:26:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-06T16:26:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2909f8f07700a5ac5e736b31d18dea8608cd89c8'/>
<id>urn:sha1:2909f8f07700a5ac5e736b31d18dea8608cd89c8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Move the "real families" code into tor-netdir.</title>
<updated>2021-12-06T15:48:27Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-06T15:48:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2c2f774bd1f1d5b30eddd4a95a0f0b102a7651c8'/>
<id>urn:sha1:2c2f774bd1f1d5b30eddd4a95a0f0b102a7651c8</id>
<content type='text'>
Just as `in_same_family` is a member of Relay, so the function for
getting all the real family members of a relay should belong in the
same crate.

This change also removes the `family()` accessor: it gives the _claimed_ family rather
 than the _acknlowedged_ family, and is therefore a bit dangerous.

 There's still a hole in this logic; I've noted it in the Limitations
section.  If we get a microdescriptor for a relay in between creating
and using  the guard restriction, it might be omitted from the family
list.
</content>
</entry>
<entry>
<title>Implement guard family restriction code</title>
<updated>2021-12-06T14:05:48Z</updated>
<author>
<name>Neel Chauhan</name>
<email>neel@neelc.org</email>
</author>
<published>2021-11-22T22:51:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b0016682c30b6db5b9180a17852c00603b40e715'/>
<id>urn:sha1:b0016682c30b6db5b9180a17852c00603b40e715</id>
<content type='text'>
</content>
</entry>
</feed>
