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 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. 2024-02-20T14:37:00Z Nick Mathewson nickm@torproject.org 2024-02-12T17:23:52Z urn:sha1:07373d8c0990748ea89cc600882168f08787cab5 This lets us check long_lived_ports only when we are constructing a TargetCircUsage, and lets us remember whether or not the circuit we've built is suitable for non-long-lived ports. It also lets us decide whether existing circuits are compatible with new requests. Closes #1100. 2024-02-20T14:37:00Z Nick Mathewson nickm@torproject.org 2024-02-12T16:42:29Z urn:sha1:2646d0caf99697d87c881c4826ef1d10587a6215 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. 2023-11-29T18:51:30Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-11-29T18:44:06Z urn:sha1:d67519d71b2f452dcc947acc12b3bdc50e3e7920 These messages are very verbose and I doubt anyone will want them, usually, even when debugging. 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-04-06T13:05:12Z Nick Mathewson nickm@torproject.org 2023-04-06T13:00:41Z urn:sha1:43e1128cdf722d183f337ac36dd3d944259b3e8d This resolves a few dead-code warnings. Closes #801. 2023-03-28T14:49:45Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-28T13:16:17Z urn:sha1:00e522a91ac1ecd59f48dc97a64319d748f2c482 Now nailing-cargo +stable clippy -p tor-hsclient --all-features --all-targets actually works. squash! Add some missing imports 2023-03-22T16:35:41Z Nick Mathewson nickm@torproject.org 2023-03-21T13:04:29Z urn:sha1:19a229155cbcc0fa16e4e03a6c03b8e6a65ae38d This uncovered a bug: NoUsage wasn't correct for Hs circuits because of its behavior with channel_usage(). 2023-03-22T15:52:17Z Nick Mathewson nickm@torproject.org 2023-03-15T14:41:07Z urn:sha1:dce4da55ae20d4867d5caf79adc6402fe03559bd This only builds the first 3 hops. It can be extended to a fourth hop later -- or not, depending on the circuit kind.