mirrors/arti.git/crates/tor-netdir/src, branch arti-v1.1.3mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.32023-03-30T14:53:51Ztor-netdir: Implmeent HsDirRing::find_pos2023-03-30T14:53:51ZIan Jacksonijackson@chiark.greenend.org.uk2023-03-30T13:37:19Zurn:sha1:577940853f04ee120d4c5e95032e7ee5201a6649tor-netdir: Make the hsdir ring be a TiVec2023-03-30T14:43:48ZIan Jacksonijackson@chiark.greenend.org.uk2023-03-30T13:31:07Zurn:sha1:db968033cfd887e33b52130ac79072b695d46ee9
This eliminates an untyped `usize` index.
tor-netdir: Use `pos` not `idx` in test network constructors2023-03-27T16:32:16ZIan Jacksonijackson@chiark.greenend.org.uk2023-03-27T16:22:31Zurn:sha1:9940bd1eb468d29ab3650a2751c024924f9e5811
There are too many things called "index" here. `idx` could be read to
mean the table index `RouterStatusIdx`, the hsdir hash `HsDirIndex`,
or an entry in some other one of these tables.
Here's, it's just the sequence number of the index in the test netdir.
Use `pos` for that. (`seq` would have been another possibility.)
tor-netdir: Use `hsdir_index` for hidden service directory hashval (fmt)2023-03-27T16:32:16ZIan Jacksonijackson@chiark.greenend.org.uk2023-03-27T16:32:04Zurn:sha1:4da12a26a9d9f874429bed00c6bf5a7f36f51726tor-netdir: Use `hsdir_index` for hidden service directory hashval2023-03-27T16:31:23ZIan Jacksonijackson@chiark.greenend.org.uk2023-03-27T16:16:08Zurn:sha1:325526a90356aaf11a58660b8f820aeb2b1f1589
The hidden services directory hashring is a ring of hsdir relays,
sorted by a hash that the spec calls the "index". That's `HsDirIndex`.
This was a bad idea because the word "index" is seriously overused,
but in Arti we must use the same terminology.
At least, qualify it everywhere. Now one of these hsdir sort position
hashes is always, in our code, an `hsdir_index`.
I think this is necessary even inside modules called `hsdir_*`,
because those can deal with other kind of "index" too.
tor-netdir: eliminate ref to abolished MdEntry2023-03-27T16:26:51ZIan Jacksonijackson@chiark.greenend.org.uk2023-03-27T16:20:33Zurn:sha1:a746e17c8eb8f63b433b32e881a2dbb7e1000117
This was removed in c3e74973b4201f71275d8cf4c0c954cfb8d0eba5
netdir: Use an even smaller rep for list of microdescs
tor-netdir: Use `rsidx` consistent for `RouterStatusIdx`2023-03-27T16:25:52ZIan Jacksonijackson@chiark.greenend.org.uk2023-03-27T15:47:52Zurn:sha1:99ffb89b487d7ced28c572b1c76b477839f62393
This is an `IndexVec` key type. Some places used `idx`, some `rsi`,
some `rs_idx`.
Use `rsidx` for it everywhere, including in locals, function names,
and fields. `rsidx` is a compromise. `rsi` might be a bit opaque,
but we want a one-"word" name since it appears inside other names.
Upgrade to bitflags 2.02023-03-13T12:47:14ZNick Mathewsonnickm@torproject.org2023-03-13T12:47:14Zurn:sha1:d6bb8fee0b3f010902d8297f16589467d82e4e4f
This version of bitflags now requires us to explicitly list the
traits that we want to derive for our bit-flags structs.
Rename onion-* cargo features to hs-* in tor-* crates2023-02-28T11:10:17ZIan Jacksonijackson@chiark.greenend.org.uk2023-02-24T14:26:25Zurn:sha1:f63c7c48afd94fe9d09746f0b76fbaff8d4a1a79
Fixes #756
Fix minimal-versions (.then_some is too new)2023-02-09T16:07:16ZIan Jacksonijackson@chiark.greenend.org.uk2023-02-09T15:21:04Zurn:sha1:3d6e6fcf0d42b42f5b9bc923cafdeb97246764ed