summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | Merge branch 'p2-flatten-flatten' into 'main'Ian Jackson2025-10-223-3/+41
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | tor-netdoc: allow NetdocParseableFields within NetdocParseableFields See merge request tpo/core/arti!3377
| * | | | tor-netdoc: Document new feature in semver.mdIan Jackson2025-10-221-0/+1
| | | | |
| * | | | tor-netdoc: NetdocParseableFields derive: support flatten (test)Ian Jackson2025-10-221-0/+11
| | | | |
| * | | | tor-netdoc: NetdocParseableFields derive: support flattenIan Jackson2025-10-221-2/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows a NetdocParseableFields inside a NetdocParseableFields. The code is rather duplicative with the NetdocParseable implementation. This is due to limitations in derive-deftly; see https://gitlab.torproject.org/Diziet/rust-derive-deftly/-/merge_requests/525 where I'm trying to start to address them.
| * | | | tor-netdoc: NetdocParseableFields derive: break out kw variableIan Jackson2025-10-221-1/+3
|/ / / / | | | | | | | | | | | | We're going to reuse this.
* | | | Merge branch 'nd-preamble' into 'main'Ian Jackson2025-10-225-71/+83
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | tor-netdoc: Rename consensus Header to Preamble, etc. See merge request tpo/core/arti!3378
| * | | | tor-netdoc: Preamble: Fix garbled doc commentIan Jackson2025-10-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3378#note_3277957
| * | | | tor-netdoc: Preamble: rename relay_version field to server_versionIan Jackson2025-10-224-8/+9
| | | | | | | | | | | | | | | | | | | | This makes it match the protocol and the spec.
| * | | | tor-netdoc: Say Preamble doesn't contain vote-status, in summary.Ian Jackson2025-10-221-1/+1
| | | | |
| * | | | tor-netdoc: Explain that Preamble doesn't contain vote-status either.Ian Jackson2025-10-221-1/+1
| | | | |
| * | | | tor-netdoc: Document breaking changes in semver.mdIan Jackson2025-10-221-0/+2
| | | | |
| * | | | tor-netdoc: netstatus: Preamble: Name the protocols fields in docIan Jackson2025-10-221-0/+2
| | | | |
| * | | | tor-netdoc: netstatus: Preamble: rename shared rand fields to match docIan Jackson2025-10-223-18/+18
| | | | | | | | | | | | | | | | | | | | | | | | | We should use the same name everywhere, even if the name in the spec is clumsy (as it is here).
| * | | | tor-netdoc: Move ConsensusFlavor into Consensus structIan Jackson2025-10-223-14/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We're going to want to apply the parse2 derive to Preamble, but this field is anomalous. Rather than trying to make it regular, simply move it to the old-parser-specific Consensus struct.
| * | | | tor-netdoc: Declare intent not to apply parse2 to ConsensusIan Jackson2025-10-221-4/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Consensus is not going to be easy to square with parse2 - especially, signature handling is very different between the two parsers. Instead, we'll have a new NetworkStatus type.
| * | | | tor-netdoc: Rename consensus Header to PreambleIan Jackson2025-10-224-40/+42
| | | | | | | | | | | | | | | | | | | | | | | | | There is no such thing as the "header" according to the spec. We mean the preamble.
* | | | | Merge branch 'ctrl-msg-2' into 'main'David Goulet2025-10-222-111/+113
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | proto: Move the control channels to RelayReactor See merge request tpo/core/arti!3387
| * | | | proto: Replace select! with select_biased!Gabriela Moldovan2025-10-221-2/+2
| | | | | | | | | | | | | | | | | | | | We need to give the control channels higher priority here.
| * | | | proto: Update an outdated doc linkGabriela Moldovan2025-10-221-1/+1
| | | | |
| * | | | proto: Add debug log when RelayReactor shuts downGabriela Moldovan2025-10-221-2/+14
| | | | |
| * | | | proto: Replace futures::select with importGabriela Moldovan2025-10-221-2/+2
| | | | |
| * | | | proto: Remove no-longer relevant note on control message handlingGabriela Moldovan2025-10-221-10/+0
| | | | |
| * | | | proto: Remove an already-addressed TODOGabriela Moldovan2025-10-221-2/+0
| | | | |
| * | | | proto: Handle control messages in RelayReactorGabriela Moldovan2025-10-222-51/+53
| | | | | | | | | | | | | | | | | | | | Control messages are handled in RelayReactor instead of BackwardReactor.
| * | | | proto: Move the control channels to RelayReactorGabriela Moldovan2025-10-222-53/+53
| | | | | | | | | | | | | | | | | | | | | | | | | This only moves the control/command fields to RelayReactor. The next step is to actually implement the control message handling and dispatch.
* | | | | Merge branch 'tor-dirserver-msrv-1.86' into 'main'David Goulet2025-10-221-1/+1
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | tor-dirserver: Bump MSRV from 1.83 to 1.86 See merge request tpo/core/arti!3385
| * | | | tor-dirserver: bump MSRV from 1.83 to 1.86hashcatHitman2025-10-211-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I noticed that when doing `cargo generate-lockfile` in the workspace root, it was locking dependencies to 1.83 compatible versions. It turns out tor-dirserver started on MSRV 1.83 after we already bumped to 1.85, and has been missed in MSRV updates ever since. I've found no indication it is intentionally getting this special treatment and am assuming it is a mistake. Signed-off-by: hashcatHitman <[email protected]>
* | | | | Merge branch 'p2-shared-rand-status' into 'main'Ian Jackson2025-10-225-17/+28
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | impl ItemValueParseable for SharedRandStatus See merge request tpo/core/arti!3380
| * | | | | tor-netdoc: impl ItemValueParseable for SharedRandStatusIan Jackson2025-10-211-0/+1
| | | | | |
| * | | | | tor-netdoc: impl Display, FromStr, NormalItemArgument for SharedRandValIan Jackson2025-10-211-2/+18
| | | | | |
| * | | | | tor-netdoc: derive From<Vec<u8>> and v-v for B64Ian Jackson2025-10-211-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This may not be the best utility type to use for lots of the fixed-length byte strings, but we *are* using it a lot in the old and now the new parser. Implement From and Into.
| * | | | | tor-netdoc: Change type of timestamp in SharedRandStatus (fmt)Ian Jackson2025-10-211-2/+1
| | | | | |
| * | | | | tor-netdoc: Change type of timestamp in SharedRandStatusIan Jackson2025-10-214-7/+8
| | | | | |
* | | | | | Merge branch 'restricted-discovery-stable' into 'main'gabi-2502025-10-224-14/+13
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | arti: Mark restricted-discovery as non-experimental See merge request tpo/core/arti!3384
| * | | | | | arti: Update README to say restricted discovery is non-experimentalGabriela Moldovan2025-10-211-1/+4
| | | | | | |
| * | | | | | arti: Move restricted-discovery closer to onion-service-serviceGabriela Moldovan2025-10-211-1/+1
| | | | | | |
| * | | | | | hsrproxy: Sort Cargo.tomlGabriela Moldovan2025-10-211-5/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This change is needed to satisfy `maint/cargo_sort`
| * | | | | | hsrproxy: Place non-experimental features at the topGabriela Moldovan2025-10-211-1/+1
| | | | | | |
| * | | | | | arti: Mark restricted-discovery as non-experimentalGabriela Moldovan2025-10-213-8/+8
| | |_|/ / / | |/| | | | | | | | | | | | | | | | As per the team decision from the 14 Oct Arti sync.
* | | | | | Merge branch 'relay-bin-4' into 'main'opara2025-10-217-43/+124
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | arti-relay: More work on bootstrapping See merge request tpo/core/arti!3375
| * | | | | | arti-relay: add line breaks between `InertTorRelay` fieldsSteven Engler2025-10-211-0/+5
| | | | | | |
| * | | | | | arti-relay: add a `MemoryQuotaTracker`Steven Engler2025-10-211-3/+12
| | | | | | |
| * | | | | | arti-relay: add a `SystemConfig` to the relay configSteven Engler2025-10-211-0/+18
| | | | | | |
| * | | | | | arti-relay: add some TODO commentsSteven Engler2025-10-211-0/+3
| | | | | | |
| * | | | | | arti-relay: small refactoringSteven Engler2025-10-211-7/+6
| | | | | | |
| * | | | | | arti-relay: generate keys only when bootstrappingSteven Engler2025-10-211-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We don't want to create new files just when creating a `InertTorRelay`. We should only generate the keys before bootstrapping.
| * | | | | | arti-relay: add note to `StorageConfig::permissions`Steven Engler2025-10-211-0/+6
| | | | | | |
| * | | | | | arti-relay: copy `state_mgr.try_lock()` from arti-clientSteven Engler2025-10-212-1/+9
| | | | | | |
| * | | | | | tor-proto: fix `clippy::needless_pass_by_value` warningSteven Engler2025-10-211-0/+1
| | | | | | |
| * | | | | | arti-relay: small change to `create_keymgr()`Steven Engler2025-10-212-30/+8
| | | | | | |