mirrors/arti.git/crates/tor-dirmgr/src/state.rs, branch arti-v1.1.9mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.92023-09-18T11:25:36Zarti-client: add exit selection with GeoIP country codes2023-09-18T11:25:36Zetator@eta.st2023-08-22T15:52:28Zurn: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 everywhere2023-08-23T09:34:00ZIan Jacksonijackson@chiark.greenend.org.uk2023-08-22T14:28:12Zurn:sha1:42df88d6bf6dbb460d2e5e1cd4838aafaffbe9acMerge branch 'clippy-allow' into 'main'2023-07-11T09:37:42ZIan Jacksoniwj@torproject.org2023-07-11T09:37:42Zurn:sha1:3acc2af4f3411588f80669ae1980679dd260b119
clippy: Allow some of our existing code patterns
See merge request tpo/core/arti!1396rng ranges: Use gen_range_infallible() for Duration::ZERO..=T2023-07-10T15:08:03ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-07T13:19:55Zurn:sha1:b151237a7f8651ed8694748832af05786a7eccfdRun maint/add_warning to actually apply new lint allows2023-07-10T12:49:51ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-10T11:19:32Zurn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0Merge branch 'event_report_everywhere' into 'main'2023-07-07T19:27:20ZNick Mathewsonnickm@torproject.org2023-07-07T19:27:20Zurn:sha1:b6b7edad593fbb245a2a31be6456c7588c56981c
Throughout: Use event_report!() macros for reporting Errors.
Closes #949
See merge request tpo/core/arti!1383Throughout: Use *_report!() macros for reporting Errors.2023-07-07T17:00:21ZNick Mathewsonnickm@torproject.org2023-07-07T13:54:27Zurn:sha1:25c6fe61e4cf230210dffdac2d3c281fcb31c5a9
I identified the cases to replace by searching for the string
`.report()`. There are a few that I didn't change:
* A couple of cases that used anyhow::Error,
* One case that reported two Errors.
* Two cases in `tor_hsclient::err` that just did
`error!("Bug: {}")`.
I have also not audited the cases in `tor-hsclient` where we're using
`tor_error::Report` manually.
Nonetheless, closes #949.
rng ranges: Use inclusive Duration ranges in several places2023-07-07T15:13:52ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-07T13:10:23Zurn:sha1:bcc3e6fef8b863fa6a863aae2d6234fba7fb99f6
Many of these call sites would panic if, somehow, the upper bound was
zero. In most cases it is very complicated to see if whether this
could happen.
However, there is a better answer:
Durations are (conceptually) dense, so picking the closed set (which
includes its boundary) rather than the open one (which doesn't) will
make little practical difference.
So change four call sites to use `..=` instead of just `..`.
dirmgr: use voting_period.2023-06-29T12:19:37ZNick Mathewsonnickm@torproject.org2023-06-26T17:32:36Zurn:sha1:f2a6754c889cb58f1090d2c6ed114be8da8cc4b3Downgrade and clarify message about dir replacment time.2023-05-08T18:01:19ZNick Mathewsonnickm@torproject.org2023-05-08T18:01:19Zurn:sha1:e6aa947c45d127faa5c2d2817b64a82d84b56403
Closes #839