mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.9 2023-10-02T18:51:27Z 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-02T12:06:08Z Nick Mathewson nickm@torproject.org 2023-10-02T12:06:08Z urn:sha1:04cca7f4fe365b6573d0fe722236a56e45a48171 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-05T16:25:24Z Nick Mathewson nickm@torproject.org 2023-09-05T16:25:24Z urn:sha1:a4badb9fdac5dd36ea173545f1ff417ccab1f49b This includes: ``` tor-basic-utils caret fs-mistrust safelog retry-error tor-events tor-units tor-geoip tor-rtcompat tor-rpcbase tor-protover tor-socksproto tor-checkable tor-congestion tor-persist tor-circmgr arti-rpcserver arti-config arti-hyper arti-bench arti-testing tor-consdiff ``` 2023-09-05T16:22:19Z Nick Mathewson nickm@torproject.org 2023-09-05T16:22:19Z urn:sha1:e251baa9a77415f3c605ff462a8ac0b3fa37660a These are: ``` hashx equix tor-async-utils tor-error tor-config tor-rtmock tor-llcrypto tor-bytes tor-hscrypto tor-hspow tor-cert tor-linkspec tor-cell tor-proto tor-netdoc tor-netdir tor-chanmgr tor-guardmgr tor-dirmgr tor-keymgr tor-hsclient tor-hsservice arti-client arti ``` 2023-09-05T12:04:26Z Nick Mathewson nickm@torproject.org 2023-09-05T11:52:25Z urn:sha1:cc8031469581d039c01efde745b1d21791426ad1 2023-08-01T14:57:55Z Nick Mathewson nickm@torproject.org 2023-08-01T14:57:55Z urn:sha1:3acdf102c705314aec63679e97240bb7d981d1c8 These crates are at version 0.x.y, so we don't need to distinguish new-feature changes from other changes: ``` tor-basic-utils fs-mistrust tor-error tor-geoip tor-checkable tor-linkspec tor-netdoc tor-netdir tor-persist tor-ptmgr tor-hsservice ``` This crate has a breaking change, but only when the semver-breaking feature `experimental-api` is enabled: ``` tor-config ``` This crate is at version 1.x.y, but has no new public APIs, and therefore does not need a minor version bump: ``` arti ``` 2023-08-01T14:51:25Z Nick Mathewson nickm@torproject.org 2023-08-01T14:51:25Z urn:sha1:6f2ae5960393b64c1d7615d2d523e050d3bebe5a These crates had first-order breaking changes: ``` retry-error tor-keymgr tor-proto tor-hsclient tor-rtmock ``` Additionally, these broke because they re-exposed RetryError: ``` tor-circmgr ``` Additionally, these broke because they may re-expose something from tor-proto: ``` arti-client tor-chanmgr tor-dirclient tor-dirmgr tor-guardmgr ``` Additionally, these broke for other fiddly reasons: `tor-ptmgr` implements traits from tor-chanmgr, which has a breaking change above. `arti-hyper` exposes types from arti-client in its API. 2023-07-07T13:00:31Z Nick Mathewson nickm@torproject.org 2023-07-06T17:52:07Z urn:sha1:a441b4e9d3ab3dde2b304d9bf721aa2c7817a7f5 This simplifies our logging a little, and implements part of