| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | Run fixup-features in preparation for release. | Gabriela Moldovan | 2024-12-02 | 10 | -9/+11 | |
| | | ||||||
| * | tor-rpc-connect: Bump thiserror to 2. | Gabriela Moldovan | 2024-11-28 | 1 | -1/+1 | |
| | | ||||||
| * | tor-persist: Bump sanitize-filename to 0.6.0. | Gabriela Moldovan | 2024-11-28 | 1 | -1/+1 | |
| | | | | | | | I couldn't find a changelog, but judging from the commit history, it looks like they've bumped their regex dep, updated their MSRV to 1.70, replaced lazy_static with OnceLock internally. | |||||
| * | tor-netdoc: Bump tinystr to 0.8.0. | Gabriela Moldovan | 2024-11-28 | 1 | -1/+1 | |
| | | | | | | According to the changelog, moving from 0.7.6 to 0.8.0 we get some new constructors and breaking changes to various "general" APIs. | |||||
| * | Merge branch 'remove-pending-on-drop' into 'main' | opara | 2024-11-28 | 4 | -38/+114 | |
| |\ | | | | | | | | | | | | | tor-chanmgr: fix `get_or_launch` cancellation safety using deferred closure Closes #1716 See merge request tpo/core/arti!2646 | |||||
| | * | tor-chanmgr: remove immediately awaited async block expression | Steven Engler | 2024-11-27 | 1 | -23/+15 | |
| | | | | | | | | | This shouldn't be needed anymore now that we use a `Defer`. | |||||
| | * | tor-chanmgr: use `Defer` in `AbstractChanMgr` to handle cancellations | Steven Engler | 2024-11-27 | 1 | -18/+23 | |
| | | | ||||||
| | * | tor-chanmgr: add `util::defer` module | Steven Engler | 2024-11-27 | 3 | -0/+79 | |
| | | | | | | | | | | | This contains the `Defer` type, which can be used to defer a closure until the `Defer` is dropped. | |||||
| * | | Merge branch 'hs-pow-feature-flag-consolidation' into 'main' | gabi-250 | 2024-11-27 | 18 | -55/+34 | |
| |\ \ | |/ |/| | | | | | PoW: Consolidate feature flags into a single flag. See merge request tpo/core/arti!2642 | |||||
| | * | PoW: Consolidate feature flags into a single flag. | Wesley Aptekar-Cassels | 2024-11-25 | 18 | -55/+34 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This replaces the hs-pow, hs-pow-full, hs-pow-v1, pow-v1, and pow-full features with a single hs-pow-full feature. It's possible that in the future we will want to split different schemes into different features, but we can do that when it comes up. For now, having this as a single flag makes it clearer what's going on, since the previous thing was not actually expressive enough to capture some things we care about (like "at least one pow scheme is enabled" that works in a future-compatible way). This change is not semver breaking since it's a experimental feature. Related: #1751 | |||||
| * | | Merge branch 'cell-lifecycle' into 'main' | gabi-250 | 2024-11-26 | 2 | -2/+2 | |
| |\ \ | |/ |/| | | | | | | | | | doc/dev/notes: cell-lifecycle: Describe the current state of things. Closes #1747 See merge request tpo/core/arti!2637 | |||||
| | * | tor-proto: Specify which of the 2 senders is used for sending cells. | Gabriela Moldovan | 2024-11-20 | 1 | -1/+1 | |
| | | | ||||||
| | * | tor-proto: Fix typo in streammap docs. | Gabriela Moldovan | 2024-11-19 | 1 | -1/+1 | |
| | | | ||||||
| * | | tor-netdoc: Error on PowParams::V1 when hs-pow-v1 is disabled. | Wesley Aptekar-Cassels | 2024-11-25 | 1 | -2/+11 | |
| | | | ||||||
| * | | tor-netdoc: Don't include pow_params in HsDesc when feature is disabled. | Wesley Aptekar-Cassels | 2024-11-25 | 2 | -7/+8 | |
| | | | ||||||
| * | | Add TODO to error if enable_pow is set but feature flag is disabled. | Wesley Aptekar-Cassels | 2024-11-25 | 1 | -0/+1 | |
| | | | ||||||
| * | | tor-hsservice: Clarify enable_pow setting TODO. | Wesley Aptekar-Cassels | 2024-11-25 | 1 | -1/+1 | |
| | | | ||||||
| * | | tor-netdir: Add timeliness param to wait_for_netdir_to_list. | Wesley Aptekar-Cassels | 2024-11-25 | 2 | -2/+3 | |
| | | | ||||||
| * | | Move helpers from tor-hsservice to tor-netdir. | Wesley Aptekar-Cassels | 2024-11-25 | 8 | -100/+95 | |
| | | | | | | | | | | | These helpers seem potentially broadly useful, and only really discoverable if they're here. | |||||
| * | | tor-hscrypto: Add Verifier::seed() helper function. | Wesley Aptekar-Cassels | 2024-11-25 | 1 | -0/+7 | |
| | | | ||||||
| * | | tor-hscrypto: Add Seed::new. | Wesley Aptekar-Cassels | 2024-11-25 | 1 | -0/+43 | |
| | | | | | | | | | | | This includes the ability to generate a seed that does not share a head with the previously used seed, which is generally what we want to do. | |||||
| * | | tor-netdoc: Support writing pow-params line. | Wesley Aptekar-Cassels | 2024-11-25 | 4 | -2/+111 | |
| | | | | | | | | | | | | | | | I'm not particularly happy with the code that does the actual writing out of the pow-params line, in particular the error handling there seems very verbose. However, I don't know of a better way to structure it given that APIs I'm working with. | |||||
| * | | TimerangeBound: Stop using std::ops::Bound. | Wesley Aptekar-Cassels | 2024-11-25 | 8 | -32/+44 | |
| | | | | | | | | | Fixes: #1691 | |||||
| * | | arti: Add onion_service.enable_pow option. | Wesley Aptekar-Cassels | 2024-11-25 | 2 | -2/+12 | |
| | | | | | | | | | This currently is not implemented. | |||||
| * | | tor-error: add comment to `ErrorKind::TransientFailure` | Steven Engler | 2024-11-21 | 1 | -0/+1 | |
| | | | ||||||
| * | | tor-chanmgr: change `RequestCancelled` retry from `Never` to `Immediate` | Steven Engler | 2024-11-21 | 1 | -1/+1 | |
| | | | | | | | | | | | | | | | If the channel request was cancelled, we should be able to retry immediately. Additionally, the `kind()` of `RequestCancelled` is `TransientFailure`, and I don't think it make sense for a transient error to return a `retry_time()` of `Never`. | |||||
| * | | tor-netdoc: add clippy allows and `#[non_exhaustive]` | Steven Engler | 2024-11-20 | 1 | -0/+2 | |
| | | | ||||||
| * | | tor-hsservice: add clippy allows | Steven Engler | 2024-11-20 | 1 | -0/+4 | |
| | | | ||||||
| * | | tor-cell: add clippy allows | Steven Engler | 2024-11-20 | 1 | -0/+1 | |
| | | | ||||||
| * | | Merge branch 'keymgr-cleanup' into 'main' | David Goulet | 2024-11-20 | 3 | -39/+4 | |
| |\ \ | | | | | | | | | | | | | tor-keymgr: Remove dead code See merge request tpo/core/arti!2638 | |||||
| | * | | tor-keymgr: Remove now-unnecessary cfg_attr. | Gabriela Moldovan | 2024-11-20 | 1 | -6/+0 | |
| | | | | | | | | | | | | | This doesn't seem to be needed anymore. | |||||
| | * | | tor-keymgr: Remove now-unnecessary clippy allows from dummy impl. | Gabriela Moldovan | 2024-11-20 | 1 | -2/+0 | |
| | | | | ||||||
| | * | | tor-keymgr: Feature-gate RelKeyPath::from_parts constructor. | Gabriela Moldovan | 2024-11-20 | 1 | -0/+1 | |
| | | | | | | | | | | | | | | | | Otherwise, we get a dead code warning when the `ctor-keystore` feature is disabled. | |||||
| | * | | tor-keymgr: Allow dead code in dummy KeyMgr. | Gabriela Moldovan | 2024-11-20 | 1 | -0/+2 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The fields are never read but need to be present in order for the dummy `KeyMgrBuilder` to have the same interface as the real one. (We could of course manually implement the builder, or let the dummy `KeyMgrBuilder` impl diverge from the real one, but for now let's leave this as-is and simply mark the fields as unused). | |||||
| | * | | tor-keymgr: Remove unused dummy error type. | Gabriela Moldovan | 2024-11-20 | 1 | -16/+1 | |
| | | | | | | | | | | | | | | | | We no longer have any dummy keymgr operations that return an error, so this error type is unused. | |||||
| | * | | tor-keymgr: Remove unused imports from dummy module. | Gabriela Moldovan | 2024-11-20 | 1 | -2/+1 | |
| | | | | ||||||
| | * | | tor-keymgr: Remove unused dummy KeyType. | Gabriela Moldovan | 2024-11-20 | 1 | -14/+0 | |
| | | | | | | | | | | | | | This is not used anywhere (or exported publicly). | |||||
| * | | | connect point: Use new CfgPathResolver api. | Nick Mathewson | 2024-11-19 | 1 | -12/+22 | |
| | | | | ||||||
| * | | | connect point: handle unrecognized auth variants. | Nick Mathewson | 2024-11-19 | 3 | -6/+39 | |
| | | | | ||||||
| * | | | Connect point: Improve robustness against new SocketAddr variants | Nick Mathewson | 2024-11-19 | 1 | -2/+10 | |
| | | | | ||||||
| * | | | connect point: add a test for ConflictingMembers. | Nick Mathewson | 2024-11-19 | 1 | -0/+13 | |
| | | | | ||||||
| * | | | connect-point: Rename Reps to Addresses. | Nick Mathewson | 2024-11-19 | 1 | -7/+7 | |
| | | | | ||||||
| * | | | connect point: Add server support. | Nick Mathewson | 2024-11-19 | 2 | -0/+71 | |
| | | | | | | | | | | | | | | | | ("Server support" here means binding to a socket and reading a cookie file.) | |||||
| * | | | connect point: Add client support. | Nick Mathewson | 2024-11-19 | 3 | -0/+182 | |
| | | | | | | | | | | | | | | | | ("Client support" here means connecting to a socket and reading a cookie file.) | |||||
| * | | | connect point: Treat unrecognized auth types as Decline. | Nick Mathewson | 2024-11-19 | 1 | -0/+9 | |
| | | | | ||||||
| * | | | connect points: Validate more correctness properties | Nick Mathewson | 2024-11-19 | 1 | -4/+23 | |
| | | | | | | | | | | | | | | | | In particular, we only allow binding/connecting to localhost, and we only support None auth for Unix connections. | |||||
| * | | | connect points: Remember original string addresses | Nick Mathewson | 2024-11-19 | 2 | -6/+59 | |
| | | | | | | | | | | | | | The cookie authentication protocol will need these. | |||||
| * | | | rpc-connect: Types for cookie authentication. | Nick Mathewson | 2024-11-19 | 3 | -1/+190 | |
| | | | | | | | | | | | | | (Cookie authentication is described in rpc-cookie-sketch.md) | |||||
| * | | | rpc-connect: Move tempdir() helper to a new module | Nick Mathewson | 2024-11-19 | 3 | -17/+36 | |
| | | | | ||||||
| * | | | RPC connect points: Facility to load from files. | Nick Mathewson | 2024-11-19 | 3 | -1/+426 | |
| | | | | ||||||
