aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
* | | Merge branch 'id-logging' into 'main'Jim Newsome2026-04-131-2/+2
|\ \ \ | | | | | | | | | | | | | | | | Tweak TunnelId and TunnelScopedCircId Display impls See merge request tpo/core/arti!3875
| * | | Tweak Display for TunnelScopedCircIdJim Newsome2026-04-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Circuit IDs (UniqId) are displayed as "Circ <x>.<y>". Prior to this MR, these TunnelScopedCircId's were displayed as "Circ <t>.<x>.<y>" where t is the integer tunnel ID. This made corresponding logs a bit confusing as to why some "Circ" identifiers had two parts and some have three, and didn't make clear that the "<x>.<y>" part of the latter were comparable with the two-part UniqIds. The previous commit effectively changes the latter to "Circ Tunnel <t>.<x>.<y>", which is still a bit confusing. This commit changes the display of TunnelScopedCircId's to "Circ <x>.<y> (Tunnel <t>)", which makes the distinction between the circuit and tunnel IDs clearer.
| * | | Tunnel ID: included "Tunnel" type-specifier in DisplayJim Newsome2026-04-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | This is akin to how circuit `UniqId`'s are prefixed with "Circ", and helps clarify logs where it isn't always clear from context whether a tunnel ID or circuit ID is being displayed.
* | | | Merge branch 'contact-info' into 'main'Clara Engler2026-04-133-3/+100
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | tor-netdoc: ContactInfo See merge request tpo/core/arti!3866
| * | | | tor-netdoc: ContactInfo: Fix unused attributeIan Jackson2026-04-091-3/+1
| | | | |
| * | | | tor-netdoc: ContactInfo: Add some roundtrip testsIan Jackson2026-04-081-0/+30
| | | | |
| * | | | tor-netdoc: ContactInfo: Use FromStr impl for netdoc item parsingIan Jackson2026-04-081-5/+15
| | | | |
| * | | | tor-netdoc: ContactInfo: derive Display tooIan Jackson2026-04-081-1/+1
| | | | |
| * | | | tor-netdoc: ContactInfo: Impose a syntax restrictionIan Jackson2026-04-081-2/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Otherwise you might, for example, receive a String from a config file, JSON API submission, RPC call, or whatever, containing a newline, and then encode it into a netdoc giving a syntax error or, worse, smuggling additional items into the document!
| * | | | tor-netdoc: ContactInfo: semver entryIan Jackson2026-04-081-0/+1
| | | | |
| * | | | tor-netdoc: ContactInfo: derive ItemValueEncodableIan Jackson2026-04-081-0/+1
| | | | |
| * | | | tor-netdoc: ContactInfo: Use d_d_adhoc technique to de-cfgIan Jackson2026-04-081-1/+3
| | | | | | | | | | | | | | | | | | | | Otherwise the cfg_attr for the field would need to name both features.
| * | | | tor-netdoc: ContactInfo: Improve doc with an xref and item nameIan Jackson2026-04-081-1/+5
| | | | |
| * | | | tor-netdoc: Add ContactInfoClara Engler2026-04-082-1/+13
| | | | |
* | | | | tor-proto: small comment improvementSteven Engler2026-04-091-1/+2
| | | | |
* | | | | tor-proto: replace a tuple with a dedicated structSteven Engler2026-04-092-18/+29
| | | | |
* | | | | tor-proto: give our ed ident to the channel reactorSteven Engler2026-04-096-5/+48
| | | | | | | | | | | | | | | | | | | | This will be needed for ntor handshakes.
* | | | | proto: Apply deferred rustfmtGabriela Moldovan2026-04-091-1/+1
| | | | |
* | | | | arti-relay: Use a SmallVec for the ntor keysGabriela Moldovan2026-04-092-2/+5
| | | | | | | | | | | | | | | | | | | | Usually, there will only be two of these.
* | | | | proto: Add method for installing ntor keys in the create handlerGabriela Moldovan2026-04-092-3/+28
| | | | | | | | | | | | | | | | | | | | | | | | | This also updates the key rotation task to call the setter whenever the ntor keys get updated.
* | | | | arti-relays: Pass a CreateRequestHandler to the crypto task (fmt)Gabriela Moldovan2026-04-091-3/+8
| | | | |
* | | | | arti-relays: Pass a CreateRequestHandler to the crypto taskGabriela Moldovan2026-04-093-1/+5
| | | | | | | | | | | | | | | | | | | | This will need to be updated each time the ntor keys change.
* | | | | arti-relay: Add tests for the ntor key rotationGabriela Moldovan2026-04-091-0/+53
| | | | |
* | | | | arti-relay: Test that 1 ntor key gets generated on first runGabriela Moldovan2026-04-091-0/+7
| | | | |
* | | | | arti-relay: Dedupe test helperGabriela Moldovan2026-04-091-16/+10
| | | | | | | | | | | | | | | | | | | | | | | | | I am about to add another one of these, so I tried to deduplicate the impls a bit.
* | | | | arti-relays: Extend existing tests to check ntor key rotation (fmt)Gabriela Moldovan2026-04-091-1/+4
| | | | |
* | | | | arti-relays: Extend existing tests to check ntor key rotationGabriela Moldovan2026-04-091-2/+6
| | | | |
* | | | | arti-relay: Generate and rotate ntor keysGabriela Moldovan2026-04-091-10/+162
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is still some outstanding work here to read the lifetime and grace period from the consensus, but that will require some bigger changes to the rotation task. Closes #2451
* | | | | arti-relay: Add callbacks for deciding whether to expire and generateGabriela Moldovan2026-04-091-11/+26
| | | | | | | | | | | | | | | | | | | | | | | | | The logic for removing and generating ntor keys is going to be slightly different here.
* | | | | arti-relay: Replace have_rotated bools with KeyChange (fmt)Gabriela Moldovan2026-04-091-8/+14
| | | | |
* | | | | arti-relay: Replace have_rotated bools with KeyChangeGabriela Moldovan2026-04-091-15/+23
| | | | | | | | | | | | | | | | | | | | This will enable us to plug in the ntor key rotation logic.
* | | | | arti-relay: Add a struct describing a key change eventGabriela Moldovan2026-04-091-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is just a wrapper over `bool` right now. It will helps us distinguish changes to the channel auth material from changes affecting the ntor circuit extension keys.
* | | | | arti-relay: s/have_rotated/have_removed for clarityGabriela Moldovan2026-04-091-2/+2
| | | | |
* | | | | relay-crypto: Add new RelayNtor key wrapperGabriela Moldovan2026-04-091-1/+6
| | | | |
* | | | | Merge branch 'ticket2440_01' into 'main'David Goulet2026-04-097-66/+91
|\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | chanmgr: Validate the ChanTarget for both client and relay Closes #2404 and #2440 See merge request tpo/core/arti!3843
| * | | | linkspec: Rename all_addrs_allowed_for_extend()David Goulet2026-04-092-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Also set a better error message when validating channel target. Signed-off-by: David Goulet <[email protected]>
| * | | | relay: Pass advertise SocketAddr to channel builder instead of IpAddrDavid Goulet2026-04-096-22/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This trickles down to the tor-proto channel handshake code. But, the real need is in the channel builder in order to validate the outbound channel target. Fixes #2440 Signed-off-by: David Goulet <[email protected]>
| * | | | chanmgr: Validate the ChanTarget for both client and relayDavid Goulet2026-04-091-41/+64
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It used to be only with the feature = relay but since client can have that feature enabled, we now validate based on channel outbound type instead. Related to #2440 Signed-off-by: David Goulet <[email protected]>
* | | | | Merge branch 'log-ids' into 'main'Jim Newsome2026-04-093-5/+13
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | Log IDs See merge request tpo/core/arti!3872
| * | | | Log socks isolationJim Newsome2026-04-081-0/+1
| | | | |
| * | | | Log tunnel and circuit IDsJim Newsome2026-04-082-5/+12
| | | | |
| * | | | Fix log typo PreeemptiveJim Newsome2026-04-081-1/+1
| | | | |
* | | | | Merge branch 'create-fast' into 'main'gabi-2502026-04-092-56/+71
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | tor-proto: Move CREATE_FAST handling to a helper See merge request tpo/core/arti!3869
| * | | | | tor-proto: take `CreateRequest` message by referenceSteven Engler2026-04-082-6/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Clippy has started warning about this since we moved the CREATE_FAST handling to a helper, so this resolves that.
| * | | | | tor-proto: move a TODOSteven Engler2026-04-081-2/+1
| | | | | |
| * | | | | tor-proto: remove old TODOSteven Engler2026-04-081-4/+1
| | | | | |
| * | | | | tor-proto: rustfmtSteven Engler2026-04-081-6/+3
| | | | | | | | | | | | | | | | | | | | | | | | Fix formatting from previous code movement.
| * | | | | tor-proto: move CREATE_FAST handlingSteven Engler2026-04-081-45/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This moves the code, changes the indentation, and wraps the result in an `Ok()`.
| * | | | | tor-proto: prepare to move CREATE_FAST handling to a helperSteven Engler2026-04-081-8/+34
| | | | | |
| * | | | | tor-proto: remove old TODOSteven Engler2026-04-081-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | This had already been resolved.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-28 21:20:48 +0000