mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.2.0 2022-02-24T14:26:38Z 2022-02-24T14:26:38Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-02-23T17:09:19Z urn:sha1:2bbd01b060f4911584e0b151db1cc63cc5bf9715 Now all of the runtime types we provide all impl<S> TlsProvider<S> where S: ... rather than merely TlsProvider<Self::TcpStream>. And we document and intent to perhaps require this in the future. 2022-01-27T20:48:30Z Nick Mathewson nickm@torproject.org 2022-01-27T20:48:30Z urn:sha1:f7373f8b2001d90a63ca08c799e9f47e8f94144d These probably aren't for things that will fail IRL, but it's nice to have coverage on the code, just in case. 2022-01-26T19:06:58Z Nick Mathewson nickm@torproject.org 2022-01-25T22:22:14Z urn:sha1:05a04220ccc4d0dcbab906db42abc97bad02f222 If we implement our own clone on CompoundRuntime, we no longer need Clone implementations on our TlsProvider implementations. 2022-01-25T18:16:39Z Nick Mathewson nickm@torproject.org 2022-01-25T18:05:37Z urn:sha1:e4e691a790dc1dfe5b45261a40674a927085c206 Also, more comments on why these limitations are safe within the context of Tor, but you wouldn't want to use them elsewhere. 2022-01-25T18:16:39Z Nick Mathewson nickm@torproject.org 2022-01-21T14:28:11Z urn:sha1:8def5a0d89603c8f1cfd91109bb439f1881d968f This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.