mirrors/arti.git/crates/tor-circmgr/src/build.rs, branch tor-llcrypto-v0.4.4mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-llcrypto-v0.4.42023-03-22T15:52:17Zcircmgr: Begin an HS circuit pool structure2023-03-22T15:52:17ZNick Mathewsonnickm@torproject.org2023-03-15T17:58:20Zurn:sha1:adafae8b3f118061789dd7cc37dcc3f072fdb913
This is now enough to launch circuits on demand. It still needs to
pre-build the first three hops, and to retry on failure.
Allow clippy::unchecked_duration_subtraction in tests2023-01-27T13:28:02ZNick Mathewsonnickm@torproject.org2023-01-27T13:01:45Zurn:sha1:a6dd92843edf2bd4c58de62a0d562921e4191ada
This panics on error, and we're fine with a panic on misbehavior in
tests.
test lint blocks: Add many many automatically2022-12-12T18:00:30ZIan Jacksonijackson@chiark.greenend.org.uk2022-12-12T17:58:40Zurn:sha1:125a455bdcca841931f33f83f206e57637ae85c4
This is precisely the result of running the rune in
maint/adhoc-add-lint-blocks.
tor-cirmgr: Replace OwnedChanTarget with LoggedChanTarget in errors2022-11-23T18:28:38ZIan Jacksonijackson@chiark.greenend.org.uk2022-11-23T15:20:18Zurn:sha1:b822e2ebe9941ba5e551b6f112239a395517def3
This
1. Makes the errors smaller
2. Redacts (currently, scrubs) the chantarget when safe logging is enabled
The other error variants in tor-circmgr::Error don't seem to contain
information that should become sensitive as part of bridge support.
tor-linkspec: Remove the old OwnedFoo::new() functions2022-10-06T19:13:05ZNick Mathewsonnickm@torproject.org2022-10-05T18:08:40Zurn:sha1:299ebd729d697cde69dc720e358abf933af2a054
These are now builders.
channel usage: Rename CU::UserTraffic from CU::Exit2022-08-17T09:54:41ZIan Jacksonijackson@chiark.greenend.org.uk2022-08-11T10:39:39Zurn:sha1:3aed28acd42dbf5342932e2f6f42cc2ddbbe8c50
As suggested in
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/657#note_2827246
Move ChannelUsage from tor_proto to tor_chanmgr2022-08-17T09:54:41ZIan Jacksonijackson@chiark.greenend.org.uk2022-08-08T15:33:33Zurn:sha1:5db974ef72eb1250ab27cd7e21141f64d8778776
Replace Channel::note_usage with Channel::engage_padding_activities,
which unconditionally causes the channel to (start to) do netflow
padding things.
The condition now lives in chanmgr.
Addresses
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/657#note_2826094
chanmgr: Use NetDirProvider::params and Arc<dyn..Netparameters>2022-08-17T09:54:41ZIan Jacksonijackson@chiark.greenend.org.uk2022-08-08T12:47:02Zurn:sha1:48fc5d3c39ccb8de3d3b52f34c5c76cae6806714
This gets rid of many Result(). Many parameters are renamed.
Test cases of the now-impossible branch are removed.
Deleting the match from padding_parameters will come in a moment.
I've split off that commit since it has much whitespace noise.
for now, change the error type to Void.
Introduce ChannelConfig2022-08-16T17:39:57ZIan Jacksonijackson@chiark.greenend.org.uk2022-07-27T19:34:43Zurn:sha1:76a1c45202cf35588780112d8400d50bd08f9926
This commit is just the necessary plumbing. The config is currently
empty. We'll add something to it, for padding control, later.
Provide ChannelUsage and plumb it all the way down2022-08-16T17:37:06ZIan Jacksonijackson@chiark.greenend.org.uk2022-07-26T18:14:12Zurn:sha1:8d44ef05dc7cd3d16f024d7b1058c16ecf54ee92
Channel padding depends on what the channel is being used for. We
therefore need to let the channel code know this information.
The implementation of the per-channel padding control logic will be in
the new note_usage function, which for now is simply a stub.
A future commit will introduce a `PaddingControlState` which lives in
the channel frontend; consult the doc comment for that type to see why
the plumbing through the channel manager terminates in the channel
frontend.