summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | tor-netdoc: signature orderliness: shuffle wording slightlyIan Jackson2026-03-191-1/+1
| | | |
| * | | tor-netdoc: signature orderliness: change terminologyIan Jackson2026-03-192-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | "Regular" is confusing, especially since in American English it tends to mean "usual" - whereas, there are no orderly signatures in Tor netdocs.
| * | | tor-netdoc: NetdocParseableSignatures: discuss orderingIan Jackson2026-03-191-0/+44
| | | |
| * | | tor-netdoc: Apply deferred rustfmt churn to importsIan Jackson2026-03-193-7/+7
| | | |
| * | | tor-netdoc: encoding: Plan for encoding signed documentsIan Jackson2026-03-191-0/+23
| | | |
| * | | tor-netdoc: parse2: Add some navigational commentsIan Jackson2026-03-191-1/+64
| | | | | | | | | | | | | | | | I have been losing my way in this file a lot. This may help.
| * | | tor-netdoc: parse2: Include body length in SignaturesDataIan Jackson2026-03-192-0/+5
| | | | | | | | | | | | | | | | | | | | This could allow users to attach and detach signatures, hash (only) the body part, etc.
| * | | tor-netdoc: parse2: Don't impl NetdocParseable for bodies of signed docsIan Jackson2026-03-196-16/+105
| | | | | | | | | | | | | | | | Such an impl is a footgun. Explain this in docs & comments.
| * | | tor-netdoc: parse2: Don't impl NetdocParseable for bodies of signed docs ↵Ian Jackson2026-03-192-4/+11
| | | | | | | | | | | | | | | | (pre-fmt)
| * | | tor-netdoc: authcert test: Avoid using NetdocParseable for AuthCertIan Jackson2026-03-191-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We want to stop deriving NetdocParseable directly for body structs. This test case does in fact parse a signed authcert and extract just the body without verifying the signatures. That's fine in a test, but we're going to make it involve some hoop-jumping. So, jump those hoops.
| * | | tor-dirserver: Avoid using NetdocParseable for consensusesIan Jackson2026-03-191-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We want to stop deriving NetdocParseable directly for body structs. Doing so reveals a call site here in tor-dirmirror where a consensus is parsed and the body data used, but without verifying the signatures. Do this explicitly with the hoop-jumping which is going to become deliberately unavoidable. Add a TODO comment because I'm not sure we have decided explicitloy that this is OK.
| * | | tor-dirserver: Avoid using NetdocParseable for consensuses (prep)Ian Jackson2026-03-191-4/+10
| | | | | | | | | | | | | | | | Formatting changes which make the next commit more readable.
| * | | tor-netdoc: parse2: Unify top-level derive as NetdocUParseablenverifiedIan Jackson2026-03-195-37/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Replace the two separate NetdocParseable and NetdocUnverified derives, for toplevel signed documents, with a single derive. This makes the derive API simpler. It will also make it reasonably possible to avoid deriving NetdocParseable directly for body structs. Such impls are a security hazard! In detail: * Rename NetdocUnverified to NetdocParseableUnverified * Have it use $IMPL_NETDOC_PARSEABLE from the NetdocParseable deftly module so that it derives NetdocParseable for the body. (We'll change this later in the series.) * Adjust the docs and all call sites.
| * | | tor-netdoc: parse2: Break out IMPL_NETDOC_PARSEABLE in a deftly moduleIan Jackson2026-03-191-161/+175
| | | | | | | | | | | | | | | | | | | | We are going to want to reuse this parsing implementation in another top-level deftly template.
| * | | tor-netdoc: parse2: Move hash out of signature items (fmt)Ian Jackson2026-03-191-17/+19
| | | | | | | | | | | | | | | | | | | | Run rustfmt and selectively apply the hunks that are relevant to the previous commit.
| * | | tor-netdoc: parse2: Move hash out of signature itemsIan Jackson2026-03-1912-84/+264
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | During encoding, including these hashes in the signature items makes no sense. The hashes are an *input* to the signature items, but not part of them. Move the hashes out of the items. Instead, provide each signatures section type with a hash accumulator type, in which the hash(es) are stored.
| * | | tor-netdoc: parse2: Move hash out of signature items (prep)Ian Jackson2026-03-193-13/+22
| | | | | | | | | | | | | | | | | | | | Nonfunctional and formatting changes which reduce noise in the next commit.
| * | | tor-netdoc: parse2: SignatureHashInputs: Include document so farIan Jackson2026-03-192-0/+5
| | | |
| * | | tor-netdoc: parse2: Introduce SignatureData structIan Jackson2026-03-199-34/+59
| | | | | | | | | | | | | | | | This is going to contain body information, and the hashes, too.
| * | | tor-netdoc: NetdocParseableSignatures: Make into its own traitIan Jackson2026-03-195-23/+26
| | | |
| * | | tor-netdoc: NetdocParseableSignatures: Make into its own macroIan Jackson2026-03-195-32/+125
| | | | | | | | | | | | | | | | | | | | | | | | This is going to be its own trait and it is usually best if macros are named after traits, rather than having the macro derive a different trait depending on meta attributes.
| * | | tor-netdoc: Add VerifyFailed::BugIan Jackson2026-03-191-0/+3
| | | | | | | | | | | | | | | | | | | | We're going to want this for cases where the hash computation machinery didn't DTRT.
| * | | tor-netdoc: Provide AsMutSelf derive macroIan Jackson2026-03-192-1/+43
| | | | | | | | | | | | | | | | We're going to want this for sets of netdoc signature hashes.
| * | | tor-netdoc: parse2 derive: break out INIT_ACCUMULATE_VARSIan Jackson2026-03-191-17/+25
| | | | | | | | | | | | | | | | For reuse when we split up the NetdocParseable derive.
| * | | tor-netdoc: parse2: netstatus poc: Improve docs slightlyIan Jackson2026-03-191-0/+3
| | | |
| * | | tor-netdoc: parse2: Give reference to what a Regular signature isIan Jackson2026-03-191-0/+2
| | | | | | | | | | | | | | | | But, all signatures in the current protocol are irregular :-/.
| * | | tor-netdoc: parse2: Fix an error messageIan Jackson2026-03-191-1/+1
|/ / /
* | | Merge branch 'ticket1596_02' into 'main'David Goulet2026-03-181-11/+48
|\ \ \ | | | | | | | | | | | | | | | | chanmgr: Add a list of unauthenticated channels See merge request tpo/core/arti!3790
| * | | chanmgr: Add a comment/TODO about channel expiryDavid Goulet2026-03-181-0/+16
| | | | | | | | | | | | | | | | Signed-off-by: David Goulet <[email protected]>
| * | | chanmgr: Support reconfigure of unauthenticated channelsDavid Goulet2026-03-181-5/+8
| | | | | | | | | | | | | | | | Signed-off-by: David Goulet <[email protected]>
| * | | chanmgr: Use the unauth_channels listDavid Goulet2026-03-181-7/+12
| | | | | | | | | | | | | | | | | | | | | | | | Put channel without relay identities in the unauth_channels list. Signed-off-by: David Goulet <[email protected]>
| * | | chanmgr: Add a list of unauthenticated channelsDavid Goulet2026-03-181-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Needed to handle client/bridge -> relay channels which are not authenticated meaning they don't have a RelayIds so they can't be put in the ListByRelayIds<>. Feature gate it to "relay" as a client will never have those kind of channels. Signed-off-by: David Goulet <[email protected]>
* | | | Merge branch 'arti-extra-everything' into 'main'Jim Newsome2026-03-181-13/+25
|\ \ \ \ | |/ / / |/| | | | | | | | | | | arti-extra build: enable everything in full and experimental See merge request tpo/core/arti!3759
| * | | arti-extra: don't include flowctl-cc or counter-galois-onionJim Newsome2026-03-181-8/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Including these would introduce flakiness, until arti#2400 is resolved. This also adds a general mechanism for omitting specific features in the arti-extra build.
| * | | arti-extra build: enable everything in full and experimentalJim Newsome2026-03-181-9/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously we enabled features piecemeal to avoid enabling `rpc`, which resulted in breakage when running under shadow. Experimentally, this appears to no longer be the case. Enabling everything in `full` and `experimental` gives us at least a little bit of testing of those features (that they don't break the build or other usage), even if we don't specifically exercise them (yet) in the CI tests.
* | | | Merge branch 'http-connect-outbound-rebased' into 'main'Nick Mathewson2026-03-188-75/+638
|\ \ \ \ | |/ / / |/| | | | | | | | | | | Http connect outbound rebased See merge request tpo/core/arti!3789
| * | | cargo fmtNihal2026-03-181-6/+9
| | | |
| * | | tor-chanmgr: add loopback validation, startup warning and httparseNihal2026-03-186-176/+334
| | | |
| * | | tor-chanmgr: split handshake into helper functionsNihal2026-03-181-14/+47
| | | |
| * | | tor-chanmgr: fix type inference in handshakeNihal2026-03-182-6/+6
| | | |
| * | | tor-chanmgr: refactor handshake into helper functionsNihal2026-03-181-30/+53
| | | |
| * | | tor-chanmgr: add base64ct dependency and docsNihal2026-03-184-8/+19
| | | |
| * | | tor-chanmgr: implement HTTP CONNECT proxy handshake and wire transportNihal2026-03-182-20/+186
| | | |
| * | | tor-chanmgr: add ProxyProtocol::HttpConnect variant and URI parsingNihal2026-03-181-36/+205
| | | |
* | | | Merge branch 'chutney-arti-extra' into 'main'Jim Newsome2026-03-186-47/+157
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | chutney test: include arti-extra bin See merge request tpo/core/arti!3772
| * | | | chutney test: include arti-extra binJim Newsome2026-03-115-20/+81
| | | | | | | | | | | | | | | | | | | | | | | | | Test the arti-extra bin, which includes most of `full` and `experimental` features, too.
| * | | | network.py: break up construction of configs listJim Newsome2026-03-111-47/+46
| | | | |
| * | | | chutney test: don't override CHUTNEY_START_TIMEJim Newsome2026-03-111-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | The default has been increased to 300, so there's no need to override it here.
| * | | | chutney ci: convert chutney-script to a normal python moduleJim Newsome2026-03-115-44/+97
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will give us a bit more flexibility, e.g. to pass additional arguments. Now that the python linters understand it, we fix some linting issues. We preserve the ability to run the test on other networks by making the Config.network optional. The new default of `None` means to use the built-in module to create the network. The functionality of the test itself is the same.
* | | | | Merge branch 'extra-info' into 'main'Clara Engler2026-03-183-1/+138
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | tor-dirclient: Support for extra-info requests See merge request tpo/core/arti!3764