mirrors/arti.git/crates/tor-chanmgr/Cargo.toml, branch arti-v0.2.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.2.02022-04-01T13:15:18ZBump all arti*, tor* crates to 0.2.02022-04-01T13:15:18ZNick Mathewsonnickm@torproject.org2022-04-01T13:15:18Zurn:sha1:5b2fc118df0524144e6b2c34fdcce3d0fb692d24
Not all of these strictly need to be bumped to 0.2.0; many could go
to 0.1.1 instead. But since everything at the tor-rtcompat and
higher layers has had breaking API changes, it seems not so useful
to distinguish. (It seems unlikely that anybody at this stage is
depending on e.g. tor-protover but not arti-client.)
Move skip_fmt into tor-basic-utils2022-03-04T11:45:24ZIan Jacksonijackson@chiark.greenend.org.uk2022-03-04T11:42:49Zurn:sha1:ebfd7349565f0f354906a78ad2ce8f8d2b88bd35
Code motion and the minimal mechanical changes.
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/375#note_2783078
Replace manual Debug impl with educe in tor-chanmgr2022-03-02T18:06:37ZIan Jacksonijackson@chiark.greenend.org.uk2022-03-02T17:10:47Zurn:sha1:f467f4666e523b9e58e2097b0f5e1b78f3e83837Bump all crates to 0.1.02022-03-01T13:59:34ZNick Mathewsonnickm@torproject.org2022-03-01T13:59:34Zurn:sha1:e8e9791a9757a32779657c5284b380ae91ca7979Expire channels that have been unused for too long2022-02-05T03:52:51ZYuan Lyulyuyuan92@gmail.com2022-02-04T04:36:01Zurn:sha1:f6f732a47818f789db76ad692d0025de1051072ftor-error: Add as a ddpendency to many crates2022-02-04T14:42:37ZIan Jacksonijackson@chiark.greenend.org.uk2022-02-03T19:06:59Zurn:sha1:6e1dc612cc9c5cf81fa5d501813f76ee9b4b7bbc
Doing this here makes it easier when I rebase/reorder things
Upgrade required version of futures crate to 0.3.142022-02-01T14:54:47ZNick Mathewsonnickm@torproject.org2022-01-28T19:50:03Zurn:sha1:c8dd73d55f69c75216ddc69fbca4283e1ae9a595
Earlier versions have a bug in UnboundedReceiver that make our new
dirclient tests fail.
Bump the patch version of every crate that changed since 0.0.32022-01-31T15:30:52ZNick Mathewsonnickm@torproject.org2022-01-31T15:30:52Zurn:sha1:01d99373089f8131d1df9758fce45ffaa3fbf659Make the native-tls crate optional.2022-01-26T19:06:58ZNick Mathewsonnickm@torproject.org2022-01-26T15:53:06Zurn:sha1:30b3818a9e31b0ebe96d4a32aa9bceb16610f994
This commit puts the native-tls crate behind a feature. The feature
is off-by-default in the tor-rtcompat crate, but can be enabled
either from arti or arti-client.
There is an included script that I used to test that tor-rtcompat
could build and run its tests with all subsets of its features.
Closes #300
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.