mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.10 2023-10-31T13:12:35Z 2023-10-31T13:12:35Z Nick Mathewson nickm@torproject.org 2023-10-31T13:00:42Z urn:sha1:537d98a12eedf5604fe28183ec603dd3609bb070 ``` These crates have new APIs: tor-async-utils ADDED tor-config ADDED tor-hscrypto ADDED tor-netdoc ADDED, plus BREAKING-experimental. These crates have patch-level changes only: tor-netdir (bugfix only). (re-exposes netdoc) arti-rpcserver (tweaks only, uses nothing that broke.) arti 1.1.10, no stable public APIs. ``` 2023-10-31T13:12:35Z Nick Mathewson nickm@torproject.org 2023-10-31T12:54:00Z urn:sha1:4460d8b3a5f801db2b20ca0e83dadd0bc8ccf5da ``` tor-basic-utils BREAKING tor-rtmock BREAKING. tor-cert BREAKING tor-cell BREAKING tor-proto BREAKING: re-exposes cell. (Also BREAKING-experimental) tor-chanmgr BREAKING: Re-exposes proto. tor-ptmgr BREAKING: re-exposes tor-chanmgr tor-guardmgr BREAKING: re-exposes proto. (Only for ClockSkew I think?) tor-circmgr BREAKING: re-exposes proto tor-dirclient BREAKING tor-hsclient BREAKING, re-exposes proto. tor-hsservice BREAKING, re-exposes proto. tor-hsrproxy BREAKING arti-client BREAKING: re-exposes proto. arti-hyper: BREAKING, re-exposes arti-client. tor-dirmgr Let's assume BREAKING, very high-level. tor-keymgr BREAKING, but experimental. ``` 2023-10-03T11:06:04Z Gabriela Moldovan gabi@torproject.org 2023-10-02T10:27:53Z urn:sha1:1360cd1c0e799daaa188327fa2f252a0faeb5017 2023-10-03T11:05:46Z Gabriela Moldovan gabi@torproject.org 2023-09-28T17:02:53Z urn:sha1:cec28a2a4acd8be80163ec63d702b3a00de3fc8a The statement ``` if hsids.all(|(_hsid, period)| rings.any(|(_, _, tp)| tp == period)) { ``` had 2 bugs: * the condition is reversed (it should be negated: we need to bail if one of the specified `hsids` cannot be found on any of our rings) * `rings.any()` mutates the `rings` iterator, causing `hs_dirs_upload` to return fewer HSDirs than expected 2023-10-02T18:55:03Z Nick Mathewson nickm@torproject.org 2023-10-02T18:55:03Z urn:sha1:0cfbb6faed2cacc46040bd0df283f31a7600c1a7 (The only change in these crates is that their dependencies changed.) 2023-10-02T18:51:27Z Nick Mathewson nickm@torproject.org 2023-10-02T18:51:27Z urn:sha1:1c3c06d68fda250dff4039614aff0be765ff68e0 2023-10-02T18:48:11Z Nick Mathewson nickm@torproject.org 2023-10-02T18:48:11Z urn:sha1:9b1e09c6bb661533081edf0bb58a57d72c92f3d9 2023-10-02T18:45:40Z Nick Mathewson nickm@torproject.org 2023-10-02T18:45:40Z urn:sha1:8a6d327ba079901aa20517b77ad9fc143a665b00 These crates have had changes that do not require their dependents to require a later version. 2023-09-18T11:25:36Z eta tor@eta.st 2023-08-22T15:52:28Z urn:sha1:a6fe895eb5c605e9c8de7ba871fc2114d65e098c This threads the country codes work through the rest of the codebase: - `tor-dirmgr` will now enable GeoIP with the embedded database when the `geoip` future is enabled - This can be extended later using the `DirMgrConfig` to allow specifying a custom database; this is not done here, though - `tor-circmgr`'s `SupportedCircUsage` and `TargetCircUsage` fields gain new `country_code` members to allow filtering circuits by country - These are `()` in builds where the `geoip` feature is not enabled -- doing it this way means we don't have to copy and paste huge swathes of code, since we can't use `#[cfg]` in patterns - `ExitPathBuilder` gains (hacked-in) support for choosing a relay with the correct country code - Due to the lack of conjuction, we just copy and paste a small bit, pending further refactoring - `StreamPrefs` now lets you specify a country code, letting embedders make use of the feature 2023-09-05T21:01:06Z Nick Mathewson nickm@torproject.org 2023-09-05T21:01:06Z urn:sha1:a05d64d7f1424f140c49a5897f05b26a1eef7c2d