mirrors/arti.git/crates/tor-netdir, branch arti-v1.1.6mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.62023-06-30T12:42:21ZBump patchlevel versions on crates with smaller changes2023-06-30T12:42:21ZNick Mathewsonnickm@torproject.org2023-06-30T12:42:21Zurn:sha1:de13a7319b7de5a336a70f128d1904954ed77f82
Done with the commands below.
The following crates have had various changes, and should get a
patchlevel bump. Since they are pre-1.0, we do not need to
distinguish new APIs from other changes.
```
cargo set-version --bump patch -p arti-client
cargo set-version --bump patch -p safelog
cargo set-version --bump patch -p tor-bytes
cargo set-version --bump patch -p tor-cert
cargo set-version --bump patch -p tor-circmgr
cargo set-version --bump patch -p tor-config
cargo set-version --bump patch -p tor-consdiff
cargo set-version --bump patch -p tor-dirclient
cargo set-version --bump patch -p tor-dirmgr
cargo set-version --bump patch -p tor-error
cargo set-version --bump patch -p tor-hsservice
cargo set-version --bump patch -p tor-linkspec
cargo set-version --bump patch -p tor-llcrypto
cargo set-version --bump patch -p tor-netdir
cargo set-version --bump patch -p tor-netdoc
cargo set-version --bump patch -p tor-proto
cargo set-version --bump patch -p tor-rpcbase
cargo set-version --bump patch -p tor-socksproto
```
This crate has new features, but no new non-experimental Rust APIs.
So even though it is post-1.0, it gets a patchlevel bump.
```
cargo set-version --bump patch -p arti
```
Bump minor versions on crates with breaking changes2023-06-30T12:38:16ZNick Mathewsonnickm@torproject.org2023-06-30T12:38:16Zurn:sha1:65e81bf0ca876669a15943caf4cf388515366623
Done with:
```
cargo set-version --bump minor -p tor-hsclient
cargo set-version --bump minor -p arti-rpcserver
cargo set-version --bump minor -p tor-hscrypto
cargo set-version --bump minor -p tor-cell
```
Mark all {hs,onion-serivce}-client features as non-experimental.2023-06-29T17:09:37ZNick Mathewsonnickm@torproject.org2023-06-29T17:09:37Zurn:sha1:d164a9dac216536bf960c7cb6a1f43d25ca55dc6netdir: add crosslinks to our definition of "usable".2023-06-29T12:53:59ZNick Mathewsonnickm@torproject.org2023-06-28T11:39:31Zurn:sha1:9790f820f7f4f021e0678e8c036314da01ae139anetdir: document what we mean by a "usable" relay.2023-06-29T12:53:59ZNick Mathewsonnickm@torproject.org2023-06-28T11:30:56Zurn:sha1:a902f320b5b31812fabc42b95a38b5453f050e7fnetdir: Conditionally expose some by_rsa APIs as experimental.2023-06-29T12:53:59ZNick Mathewsonnickm@torproject.org2023-06-28T11:10:37Zurn:sha1:7ac362eba7b51e9631d265f6280c12c2b99b8866
Network-health wants these to see whether a given relay is listed in
the consensus.
cc @juga
netdir: Remove a TODO HS2023-06-29T12:19:37ZNick Mathewsonnickm@torproject.org2023-06-26T18:15:40Zurn:sha1:76376b2abd85b650f6affee3a1c3f022cbeb0b41
The function this comment is asking us to write is `circtarget_from_pieces`.
Downgrade TODO HS on HsDirParams::compute().expect()2023-06-29T12:19:37ZNick Mathewsonnickm@torproject.org2023-06-26T18:12:55Zurn:sha1:c565a67689ba6d2b8b3f59448c66e9b4bf34e072
(Adding comments explaining that these errors are really
unlikely to occur, unless there is a bug in our code or in Rust's
time handling.)
netdir: Defer a TODO HS but add a comment2023-06-29T12:19:37ZNick Mathewsonnickm@torproject.org2023-06-26T17:52:07Zurn:sha1:768452d9e5ab5ce6a2e4298e6cff2dd57e2b2763
This issue with walking over the ring is an issue we really must
solve on the services timeframe, as is the one about looking only at
the rings for which a blinded ID is germane.
netdir: take n_replicas and spread_fetch from consensus parameters2023-06-29T12:19:37ZNick Mathewsonnickm@torproject.org2023-06-26T17:46:20Zurn:sha1:2bdf10db84a69acb73cdaf5c524348f2738800c5
This makes them configurable, since we allow the user to override
any consensus parameter.