mirrors/arti.git/crates/tor-rtcompat/src/impls/async_std.rs, branch arti-v1.2.4 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.4 2022-08-15T13:47:40Z tor-rtcompat: Require that TcpStream be Send 2022-08-15T13:47:40Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-03-25T11:11:53Z urn:sha1:740f306cb0a09274d67566c34cceaa9e63a3e66f The lack of this seems to have been an oversight. UdpSocket: remove support for connect(). 2022-03-18T19:39:40Z Nick Mathewson nickm@torproject.org 2022-03-18T19:34:51Z urn:sha1:2aa5f45bc8bb3153fca2cc9e33b7cd951e1415c4 Currently, Arti doesn't need this. But once it does, it will be way better to have a separate type for connected sockets, rather than having to error-check every time somebody gives us a socket. Part of #410 add simple unit test on UDP 2022-03-14T20:19:20Z trinity-1686a trinity@deuxfleurs.fr 2022-03-11T17:27:59Z urn:sha1:f4581ffd0438a0e07839036f36960ad41742be03 add skeleton for DNS handling 2022-03-14T19:59:35Z trinity-1686a trinity@deuxfleurs.fr 2022-03-06T16:34:13Z urn:sha1:9b3be0ad47ea5eca08596d83d3a25bd3ae0c2abf add udp to runtime 2022-03-14T19:59:33Z trinity-1686a trinity@deuxfleurs.fr 2022-03-05T18:49:38Z urn:sha1:4a44ef56c0743775d49eca138a253f11e93c7a35 Rename `SpawnBlocking` trait to `BlockOn`. 2022-01-26T19:06:58Z Nick Mathewson nickm@torproject.org 2022-01-26T18:59:37Z urn:sha1:bf8fa66d36298561cc868706f748049cec23f5eb This avoids a future confusion with the new `SpawnBlocking` trait in async_executors v0.5, and better describes what the trait provides. Refactor native_tls usage into its own module 2022-01-25T18:16:39Z Nick Mathewson nickm@torproject.org 2022-01-24T20:12:49Z urn:sha1:d1d121aac6c6dd5bd0b31ef6e01614da36071221 This change uses the async-native-tls crate for everything, and deletes some duplicated code. Refactor Runtimes to use separate TLS implementations internally. 2022-01-19T20:47:26Z Nick Mathewson nickm@torproject.org 2022-01-19T19:12:08Z urn:sha1:17920e43f84fd6c4c3f9abe77c7b477d6c17602c This will make it easier to implement them using some other TLS provider as well, without having to duplicate all of our code. Make TlsConnector wrap TCP connections, not create its own 2021-12-07T17:00:40Z eta tor@eta.st 2021-12-02T11:44:29Z urn: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. Resolve roughly half of the XXXXs. 2021-12-06T20:11:03Z Nick Mathewson nickm@torproject.org 2021-12-06T20:01:29Z urn:sha1:31b385c5b20205e879a847a9331c30a37dc2e6f5 We want to only use TODO in the codebase for non-blockers, and open tickets for anything that is a bigger blocker than a TODO. These XXXXs seem like definite non-blockers to me. Part of arti#231.