mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.4 2022-01-19T13:22:42Z 2022-01-19T13:22:42Z Nick Mathewson nickm@torproject.org 2022-01-19T13:22:42Z urn:sha1:d1c362f30873f4f937d0452fdd5d804948622770 2022-01-18T18:06:08Z Nick Mathewson nickm@torproject.org 2022-01-17T22:11:18Z urn: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. 2022-01-13T13:12:29Z Ian Jackson iwj@torproject.org 2022-01-13T13:12:29Z urn:sha1:9b723cba53852ecd3505c0cabc42ca3b5d31ad34 2021-12-28T20:15:40Z Daniel Eades danieleades@hotmail.com 2021-12-28T20:15:40Z urn:sha1:592642a9e6c1c03e525f8b452f4b97e6fd17ff9b 2021-12-14T18:45:19Z Neel Chauhan neel@neelc.org 2021-12-14T18:45:19Z urn:sha1:e67d4e08213094c74685da72db26a4e01c4d8b00 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. 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. 2021-12-04T20:42:53Z Nick Mathewson nickm@torproject.org 2021-12-04T20:42:53Z urn:sha1:66d5f73b9ca8f0d2e4f143d9c7c5a0b162bb3e73 The redundant method was a `to_owned` that probably shouldn't have been called that. It was only used in one place. The tests should get tor-linkspec's line coverage up above 90%. 2021-11-25T13:20:37Z Daniel Eades danieleades@hotmail.com 2021-11-25T13:14:05Z urn:sha1:db16d13df4779ac61005050dfe5ce05e3d5a1b5d 2021-11-04T14:54:47Z Nick Mathewson nickm@torproject.org 2021-11-04T14:54:47Z urn:sha1:dae8cdb463d94b444ecd465f3a52fdc5a8ed3ede