mirrors/arti.git/crates/tor-circmgr/src/path, branch arti-v1.2.0 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.0 2024-02-22T15:37:55Z Mark code with "TODO #504" and "TODO #789". 2024-02-22T15:37:55Z Nick Mathewson nickm@torproject.org 2024-02-20T14:49:38Z urn:sha1:01ab38232eb2e6d32a9a3a8789d3588a830e87ce I've done this by looking for every non-test instance of pick_relays or pick_n_relays, and for every non-test usage of any non-ID-related method on Relay or UncheckedRelay. Part of #504. Add a couple of TODOs about Stable-based path selection. 2024-02-20T14:37:00Z Nick Mathewson nickm@torproject.org 2024-02-12T16:42:29Z urn:sha1:2646d0caf99697d87c881c4826ef1d10587a6215 When building paths, require the Stable flag as appropriate 2024-02-20T14:37:00Z Nick Mathewson nickm@torproject.org 2024-02-12T16:35:17Z urn:sha1:aceccb1a675f5dd0661e58f580ee3398b02c7403 The Stable flag means that circuits build through a given relay are not likely to get closed precipitously. (Currently, the authorities guess this by looking at the relay's mean time between failures.) Generally speaking, paths must be Stable if: * They are going to get used for a rendezvous point. * They are going to get used for an introduction point. * They are going to get used for exiting to a member of long_lived_ports. Require the Fast flag on all randomly selected relays. 2024-02-20T14:37:00Z Nick Mathewson nickm@torproject.org 2024-02-12T15:56:31Z urn:sha1:8a92abd3b8696c542575657a61d95ba1bc4cb0c0 This matches the behavior of C tor. Part of #1100. Only pick Fast-flagged relays as directory caches 2024-02-20T14:37:00Z Nick Mathewson nickm@torproject.org 2024-02-12T15:52:15Z urn:sha1:54126746eb7c305237af686041410b2b271949b8 Matches the behavior of C tor. Part of #1100. Require that guards are Fast and Stable. 2024-02-20T14:37:00Z Nick Mathewson nickm@torproject.org 2024-02-12T15:30:39Z urn:sha1:f20669fe460332b8656421d4f331f4287b754dd7 This matches the behavior of C tor. Part of #1100. arti-client: add exit selection with GeoIP country codes 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 Run maint/add_warning to add lint block everywhere 2023-08-23T09:34:00Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-08-22T14:28:12Z urn:sha1:42df88d6bf6dbb460d2e5e1cd4838aafaffbe9ac Run maint/add_warning to actually apply new lint allows 2023-07-10T12:49:51Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-07-10T11:19:32Z urn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0 ExitPath: Add an explanation of WeightRole::Exit on non-exit circs 2023-04-12T13:50:16Z Nick Mathewson nickm@torproject.org 2023-04-12T13:50:16Z urn:sha1:2efdcd38ff009a53ea4b0b8f822c13247cf9ca75 In one case, we use WeightRole::Exit on circuits that can't actually be used to exit. This commit adds a comment to explain why, so that we don't wonder about it in the future, and we have some indication of whether it's still appropriate. Closes #785