mirrors/arti.git/crates/tor-ptmgr/src/ipc.rs, branch arti-v2.1.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.1.02025-11-06T11:28:22ZFix name of clippy lint to unchecked_time_subtraction (2)2025-11-06T11:28:22ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-06T11:23:25Zurn:sha1:a5fd5c48ea059a80cc1f6c50e248654b5ff3aaff
Run maint/add_warning
Switch Cargo.toml files to edition 2024.2025-08-07T15:28:36ZNick Mathewsonnickm@torproject.org2025-08-06T01:19:58Zurn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc
First, run
```
git grep -l "^edition =" |
xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```
Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.
Third, run cargo fmt again.
*: suppress cognitive_complexity warnings from nightly2025-05-29T14:21:17ZNick Mathewsonnickm@torproject.org2025-05-21T14:48:35Zurn:sha1:5327d3e22a83b8469a5d4191d92e1364344ddc93
Apparently clippy nightly is better (or worse?) about detecting
complex functions than before, so I'm suppressing these warnings
where they occur.
I have mixed feelings about these warnings: On the plus side,
they really do help to detect functions that are twistier than they
need to be. On the minus side, they get confused by tracing macros,
and the "allows" do pile up. But on the plus side, those "allows"
do provide a way to find functions that need to be refactored,
and they are never uglier than the functions they decorate.
Use mpsc_channel_no_memquota next to a TODO2024-10-15T11:03:18ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-09T18:19:00Zurn:sha1:507342b2119c760e9b79182bc8bfe6a04fee5509
We have a ticket for this. But the ticket number was wrong, so fix that.
memquota: Note a TODO about PT channels2024-10-02T15:05:12ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-01T16:11:46Zurn:sha1:17b4d312c433c6afa90bb29f09bed799742d5bb4ptmgr: Forbid managed pts on non-localhost2024-09-25T16:42:45ZNick Mathewsonnickm@torproject.org2024-09-25T16:42:45Zurn:sha1:51d0888479ee985593e91bdb722f0b8929fd4ca3tor-ptmgr: moved `PtClientMethod` from ipc to crate module2024-08-20T14:05:50ZSteven Engleropara@torproject.org2024-08-20T13:37:30Zurn:sha1:5774dd456265ef4cb8771342538a07ba76e5a5d9tor-ptmgr: move some code to a new 'managed' module2024-08-20T14:05:50ZSteven Engleropara@torproject.org2024-08-20T13:37:29Zurn:sha1:5db367f4b593e2baf818e571682ac04b4f823cbf
Code that's related to managed transports has been moved to a new
'managed' module. This includes the PT reactor since it's not needed for
unmanaged transports.
Add test for PtStatus containing TRANSPORT field.2024-08-01T18:50:21ZAlexander Færøyahf@torproject.org2024-08-01T18:50:21Zurn:sha1:f403de58e13372f8459a6645feabeee23c7858dc
See: tpo/core/arti#1488.
Don't require TRANSPORT for PT STATUS messages.2024-08-01T18:37:33ZAlexander Færøyahf@torproject.org2024-08-01T18:11:50Zurn:sha1:bcae275506ffc544cb8b5c3436bb006e2fc5bc3c
This patch changes the PT STATUS handler to not require the presence of
the `TRANSPORT` field in the K/V line. This matches current behaviour of
C Tor and was requested by the Anti-censorship Team at an earlier point
to enable STATUS messages to work for situation where it's not transport
specific messages.
To avoid future issues, we simply ignore any required keys right now
even though TYPE is to be expected.
See: tpo/core/torspec#267
See: tpo/core/torspec!63
See: tpo/core/arti#1488