mirrors/arti.git/crates/tor-proto/src/relay/reactor, branch mainmirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=main2026-08-03T18:27:50Zproto: Move comment to the right place2026-08-03T18:27:50ZDavid Gouletdgoulet@torproject.org2026-08-03T17:50:55Zurn:sha1:220f153156118dd05475cced512a7479a2686de8
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Add {backward|forward} prefix to circ_id in logs2026-08-03T18:27:50ZDavid Gouletdgoulet@torproject.org2026-08-03T17:47:56Zurn:sha1:c241916c931a7e9c0970e6db643689c2b39468d0
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Rename uniq_id to circ_unique_id mostly in logging2026-08-03T18:27:50ZDavid Gouletdgoulet@torproject.org2026-08-03T17:22:33Zurn:sha1:b772cecf5d5bee7e3eea0ca652e4befdeee4ed29
We have decided that instead of "uniq_id" in logging, we'll use the
"<domaine>-[<type>]-id" syntax to indicate who is that unique ID.
This commit only renames circuit's unique ID to "circ_uniq_id".
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Log both UniqId and CircId when possible2026-08-03T18:27:50ZDavid Gouletdgoulet@torproject.org2026-07-29T14:43:38Zurn:sha1:996f0448223011b6948d2197706b0fcf8b3dfc2d
This commit only affects logging. Whenever possible, log both the UniqId
and CircId.
This also changes the log lines which is now "uniq_id=" and "circ_id="
as the UniqId is internal and circ_id (CircId) is protocol level.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Rename CircId and UniqId variable name2026-08-03T18:25:23ZDavid Gouletdgoulet@torproject.org2026-07-29T14:03:13Zurn:sha1:cc838ad3312d491c406fdc06c2971c006c4cf5f5
A CircId is now a circ_id and a UniqId is a unique_id so we stop
confusing them in the code.
Furthermore, channel_id that are CircId are now circ_id. Channel IDs are
different and encoded internally into a UniqId.
This is the first step to clarify semantic before we change the logging
to log both unique ID and circ ID.
No behavior change.
Signed-off-by: David Goulet <dgoulet@torproject.org>
tor-proto: pass correct chan msg cmd to `decrypt_outbound()`2026-06-24T17:09:18ZSteven Engleropara@torproject.org2026-06-24T15:16:49Zurn:sha1:9f335acf7b0426fba583a68ab4b15d25cc6d9531
Instead of converting the `RelayEarly` message to a `Relay` message, we
add a new `RelayMaybeEarlyChanMsg` restricted message set that can hold
either.
Previously we were passing the wrong channel message command to
`decrypt_outbound()`, which would cause the decryption to fail for relay
crypto algorithms that use the command.
proto: Remove TODOs about flushing pending data2026-05-26T20:29:30ZGabriela Moldovangabi@torproject.org2026-05-26T20:29:30Zurn:sha1:c508f738d0e4d4b8474acd1d7bef97d36d137984
We decided the reactor is the wrong place to handle this.
See discussion in #2490
proto: Remove unused async2026-05-20T14:45:30ZGabriela Moldovangabi@torproject.org2026-05-14T17:42:12Zurn:sha1:46d45fee0d3c753741673c533ae54f1d8d97a4adproto: Make TRUNCATE trigger a proto violation2026-05-20T14:45:30ZGabriela Moldovangabi@torproject.org2026-05-14T17:41:43Zurn:sha1:8d7e8680ae34f27a1e073cdc64b2d7e66645365bproto: Add a comment clarifying why we don't need to propagate DESTROY2026-05-20T14:45:30ZGabriela Moldovangabi@torproject.org2026-05-14T15:51:01Zurn:sha1:288f98a2e4770e1f68b395a97ca7947fc175e121