mirrors/arti.git/crates/tor-circmgr, branch arti-v1.2.4mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.42024-06-05T15:06:54ZBump all the unstable tor- and arti- crates to 0.19.2024-06-05T15:06:54ZGabriela Moldovangabi@torproject.org2024-06-05T15:06:54Zurn:sha1:7a11638841eeabd2b5ebfe307541926c29cbfe77
The unstable crates are:
- tor-error
- tor-config
- tor-units
- tor-geoip
- tor-rtcompat
- tor-rtmock
- tor-log-ratelim
- tor-rpcbase
- tor-memquota
- tor-llcrypto
- tor-protover
- tor-bytes
- tor-hscrypto
- tor-socksproto
- tor-checkable
- tor-cert
- tor-linkspec
- tor-cell
- tor-proto
- tor-netdoc
- tor-consdiff
- tor-netdir
- tor-relay-selection
- tor-persist
- tor-chanmgr
- tor-ptmgr
- tor-guardmgr
- tor-circmgr
- tor-dirclient
- tor-dirmgr
- tor-keymgr
- tor-hsclient
- tor-hsservice
- tor-hsrproxy
- arti-client
- arti-rpcserver
- arti-hyper
- tor-basic-utils
- tor-async-utils
Done using
```
for p in "${unstable[@]}"; do cargo set-version -p $p 0.19; done
```
where `unstable` contains the list above
tor-circmgr: Explicitly handle all VanguardMode variants.2024-06-05T09:43:53ZGabriela Moldovangabi@torproject.org2024-06-05T09:43:53Zurn:sha1:47a1370a91b6243c5bc76f608134d448a93815ee
This is less error-prone than the alternative.
tor-circmgr: Reference a ticket number in a refactoring TODO.2024-06-05T09:39:27ZGabriela Moldovangabi@torproject.org2024-06-05T09:39:27Zurn:sha1:838e3a4a9ddace27d0c34e613c26e27c1ee37acdtor-circmgr: Note that guard_and_target exclusion sometimes doesn't exclude target.2024-06-05T09:38:11ZGabriela Moldovangabi@torproject.org2024-06-05T09:35:36Zurn:sha1:7fd813c93037e7e48060d361238a5f62c4f7c6f3tor-circmgr: Exclude the target when extending SHORT stubs.2024-06-04T19:50:40ZGabriela Moldovangabi@torproject.org2024-06-04T19:45:48Zurn:sha1:736fa9a359c8d2b9075ed6f7f4e315191c6e54ce
When extending SHORT circuit stubs, the last hop shouldn't be the same
as the circuit target.
tor-circmgr: Exclude the target relay when building vanguards circuits.2024-06-04T19:02:18ZGabriela Moldovangabi@torproject.org2024-06-04T18:24:01Zurn:sha1:f456d8c530e252c8fcf38b74575543771766063c
Otherwise, some of the circuits will fail (because if the target is
selected as one of the L2, L3, or M hops, it won't be able to extend the
circuit to itself).
tor-circmgr: Apply deferred fmt.2024-06-04T15:49:07ZGabriela Moldovangabi@torproject.org2024-06-04T15:49:07Zurn:sha1:be5795b7316dfcb975116675a45a4f28b217b200tor-circmgr: Add TODOs about improving circuit length checks.2024-06-04T15:42:48ZGabriela Moldovangabi@torproject.org2024-06-04T12:25:00Zurn:sha1:051dd2d65d5f20f03091d5a892e0e1930f856f07tor-circmgr: Remove HsPool::vanguards_enabled() (fmt).2024-06-04T15:41:05ZGabriela Moldovangabi@torproject.org2024-06-04T13:34:53Zurn:sha1:ffcc7b4734bd8804bcc260c6ae5d530e204568d4tor-circmgr: Remove HsPool::vanguards_enabled().2024-06-04T15:39:03ZGabriela Moldovangabi@torproject.org2024-06-04T12:02:25Zurn:sha1:95aad85933b9b6157e75983dbc3c96e7f19e32ae
Previously, the HsCircPool had a bug that caused SHORT lite-vanguards
circuits to be incorrectly extended by one hop when being repurposed as
EXTENDED circuits (EXTENDED circuits only need to be extended by extra
hop if full vanguards are in use).
Closes #1456 and #1458