mirrors/arti.git/crates/tor-ptmgr/src, branch arti-v1.2.7mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.72024-08-28T14:27:46Zextract tor_async_utils::oneshot into ::oneshot-fused-workaround2024-08-28T14:27:46ZJim Newsomejnewsome@torproject.org2024-08-22T19:20:36Zurn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1
Having this in the `tor-async-utils` crate prevents us from doing both
of the following without introducing a circular dependency:
* using it in `tor-rtmock` (which we currently do, particularly in
tests).
* using `tor-rtmock` to test things in `tor-async-utils`. We don't do
this yet, but it is generally sensible to do so. In particular we
want to move the `stream_peak` module there, which is currently tested
with `tor-rtmock`.
Moving this into its own crate avoids this circular dependency.
tor-ptmgr: added a 'managed-pts' default feature2024-08-21T17:17:50ZSteven Engleropara@torproject.org2024-08-20T13:37:31Zurn:sha1:803b52f6f3326047ebb7c88e5f5a75e6323d7a33
This conditionally compiles most of the code related to managed
transports.
tor-ptmgr: break out `spawn_transport` into separate function2024-08-20T14:06:56ZSteven Engleropara@torproject.org2024-08-20T13:37:30Zurn:sha1:1526923a4a849f5a07e395adb2d74df7fcb332a8tor-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.
tor-ptmgr: fix warnings when 'tor-channel-factory' isn't enabled2024-08-20T14:05:48ZSteven Engleropara@torproject.org2024-08-20T13:37:28Zurn:sha1:aacbd4d279a7f5653f32a61cbbd0612f6928079dtor-ptmgr: added the `TransportOptions` enum2024-08-20T14:05:08ZSteven Engleropara@torproject.org2024-08-20T13:37:27Zurn:sha1:a391c643477420f2e8b602700268debd053b42b5
This is a little nicer and more type-safe to work with than
`TransportConfig`. It would have been nice to change `TransportConfig`
directly instead, but it would slightly change arti_client's public API,
and would require an extra field in the `[[bridges.transports]]` toml
table.
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
Re-run maint/add_warning.2024-05-06T13:31:35ZNick Mathewsonnickm@torproject.org2024-05-06T13:23:41Zurn:sha1:97f452ec9958bf7d8ca3275c39655814a4494637
This commit is automatically generated.