mirrors/arti.git/crates/tor-relay-selection, branch arti-v1.4.4mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.42025-06-05T10:33:57Zrelease: Bump all tor-/arti- crates to 0.31.0.2025-06-05T10:33:57ZAlexander Hansen Færøyahf@torproject.org2025-06-05T10:33:57Zurn:sha1:95180f80d7ab574a95368f3bca1e7b78555d479a
This was done using:
for crate in $(./maint/list_crates | grep -P '^tor-|^arti-'); do
cargo set-version -p $crate 0.31.0
done
relay-selection: Rename RendPoint usage to NewRendPoint.2025-05-20T19:22:08ZNick Mathewsonnickm@torproject.org2025-05-20T14:08:56Zurn:sha1:5a963c342102793828a2b1d9cada1cb717c70409
This mirrors NewIntroPoint, and helps us to remember that we only
want to use this usage when we're a client that's picking a
rendezvous point; we don't want to enforce it when we're a relay
connecting to a client-selected rendezvous point.
relay-selection: tweak messages about rejection reasons2025-05-20T19:22:08ZNick Mathewsonnickm@torproject.org2025-05-20T13:29:04Zurn:sha1:5718784ad05e6d3ec2b11bb5abed809874840843
"Useless as xyz" implies that the relay wouldn't work at all as a
middle relay, but that's not true: it _would_ work somewhat, but be
can't use it for some other reason.
netdir, relay-selection: require Fast and Stable for rendpoints.2025-05-20T19:22:08ZNick Mathewsonnickm@torproject.org2025-05-20T13:07:29Zurn:sha1:c51745d1d0cdfb3363d8b505c7c749f70276ab57
Since we don't know what kind of traffic we'll use a rendezvous
point for, we don't want to use it if it isn't "Fast" (reasonably
high bw) and "Stable" (unlikely to crash soon).
hs: Prevent a client from using a `MiddleOnly` relay for onion services2025-05-20T19:22:08ZNeel Chauhanneel@neelc.org2025-04-03T00:38:04Zurn:sha1:94baab29f330fd17269e6b44958896b3f9ca794a
> The actual impact of this patch is to prevent usage of MiddleOnly
> relays as Introduction Points. The Rendezvous Point logic isn't
> hooked up yet - nick
All crates: bump rust-version to 1.83.2025-05-13T18:46:28ZNick Mathewsonnickm@torproject.org2025-05-13T18:46:28Zurn:sha1:88e911acd4bb70bf1da0fc71d77b51cb6abde478release: Bump all unstable tor/arti crates to 0.30.02025-05-01T16:22:28ZWesley Aptekar-Casselsme@wesleyac.com2025-05-01T15:55:57Zurn:sha1:770aaa9648d42835b2c6b3b29f4051d287ddba88
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.30.0
done
```
Update rand requirement to 0.9.12025-04-29T22:52:26ZNick Mathewsonnickm@torproject.org2025-04-29T19:04:27Zurn:sha1:fc0810c1091b2ec606111ae94e726cf5f7b10b38
(This is going to be a _requirement_,
since rand 0.9.1 has a behavioral change from 0.9.0)
Run cargo update.2025-04-29T21:35:34ZWesley Aptekar-Casselsme@wesleyac.com2025-04-29T17:30:17Zurn:sha1:54e3933f577548f10e01ae9e979ffb110481f9b4
I updated everything except rand, because the new version of rand
interacts with #1903, thus requiring more care.
Bump all the unstable tor- and arti- crates to 0.29.0.2025-03-31T17:59:51ZGabriela Moldovangabi@torproject.org2025-03-31T17:34:50Zurn:sha1:1be579f99a7c0784bd7710f9ee6ee9a6b10c85df
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.29.0
done
```