mirrors/arti.git/crates/tor-chanmgr/src/builder.rs, branch derive-traitsmirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=derive-traits2022-02-16T16:55:47Ztor-chanmgr: use Bug types.2022-02-16T16:55:47ZNick Mathewsonnickm@torproject.org2022-02-15T19:19:03Zurn:sha1:caa70fde35b6a973ae2b29bf4760c5e019c14911Merge branch 'error-improvements' into 'main'2022-02-08T14:42:30Zetator@eta.st2022-02-08T14:42:30Zurn:sha1:109515ecfe587a65f0920e074cdd593d3810cd97
Hopefully uncontroversial improvements to new Error code
See merge request tpo/core/arti!291Expire channels that have been unused for too long2022-02-05T03:52:51ZYuan Lyulyuyuan92@gmail.com2022-02-04T04:36:01Zurn:sha1:f6f732a47818f789db76ad692d0025de1051072fMake SpawnError wrappers contain a 'spawning' string2022-02-04T21:06:11ZNick Mathewsonnickm@torproject.org2022-02-04T20:39:12Zurn:sha1:070e52653d9a49fe561e9ce119881f696baa325e
(By our convention, these errors should say what we were trying to
spawn when the error occurred.)
channel errors: Include what we were doing2022-02-04T15:03:19ZIan Jacksonijackson@chiark.greenend.org.uk2022-02-04T15:03:01Zurn:sha1:6c2f9dac16f3c550b2286fad3b8dce97cb7ba8e0tor-chanmgr: Handle IO errora in the new style2022-02-04T14:42:37ZIan Jacksonijackson@chiark.greenend.org.uk2022-01-26T15:44:12Zurn:sha1:2a471ffd1a1d70ed585067d2e1dc1bf94b8f3103
Two ? in the tests become expects, which will do. That avoids having
to construct a proper error with context here.
tor-chanmgr: Add bootstrap/status reporting.2022-01-18T18:06:08ZNick Mathewsonnickm@torproject.org2022-01-17T22:11:18Zurn:sha1:c162e57e29a3bfd1f0e793b25d8c986a96a0a474
The information is pretty basic here: we use "have we been able to
connect/TLS-handshake/Tor-handshake" as a proxy for "are we on the
internet? Are we on a reasonably unfiltered part of the internet?"
Eventually we'll want to make the information gathered and exported
more detailed: I've noted a few places in the code. For now,
however, this is about as good as C Tor does today, and it should be
a good starting point.
This uses a slightly different design from tor-dirmgr. Instead of
exporting an entire state structure via `postage::watch`, it exports
only the parts of that structure which the user is supposed to
read. I think that's more reasonable in this case because most of
the possible internal transitions in the tor-chanmgr state don't
cause a change in the exposed status.
chanmgr: get rid of Arc around Channel2022-01-13T13:12:29ZIan Jacksoniwj@torproject.org2022-01-13T13:12:29Zurn:sha1:9b723cba53852ecd3505c0cabc42ca3b5d31ad34tor-chanmgr: Fix happy eyeballs comment grammar in builder.rs2021-12-14T18:45:19ZNeel Chauhanneel@neelc.org2021-12-14T18:45:19Zurn:sha1:e67d4e08213094c74685da72db26a4e01c4d8b00Make TlsConnector wrap TCP connections, not create its own2021-12-07T17:00:40Zetator@eta.st2021-12-02T11:44:29Zurn:sha1:b14c5f370eef0a4fc1d2504ce54de1a921472567
`tor-rtcompat`'s `TlsConnector` trait previously included a method to
create a TLS-over-TCP connection, which implied creating a TCP stream
inside that method. This commit changes that, and makes the function
wrap a TCP stream, as returned from the runtime's `TcpProvider` trait
implementation, instead.
This means you can actually override `TcpProvider` and have it apply to
*all* connections Arti makes, which is useful for issues like arti#235
and other cases where you want to have a custom TCP stream
implementation.
This required updating the mock TCP/TLS types in `tor-rtmock` slightly;
due to the change in API, we now store whether a `LocalStream` should
actually be a TLS stream inside the stream itself, and check this
property on reads/writes in order to detect misuse. The fake TLS wrapper
checks this property and removes it in order to "wrap" the stream,
making reads and writes work again.