mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-dirmgr-v0.5.1 2022-07-08T17:26:18Z 2022-07-08T17:26:18Z eta tor@eta.st 2022-06-23T13:51:01Z urn:sha1:af64a0a984cb357c0b60cea650ca90d8d1c6240d This implements a higher-level API for the ntor v3 handshake, in line with that exposed by the ntor handshake. It does not, however, use the existing `ClientHandshake` trait, due to fundamental differences in the handshakes (namely, that the v3 handshake can include some additional extra extension data). Currently, the higher-level API assumes circuit extension, and copies the (undocumented!) magic verification string from c-tor that indicates this usage. A rudimentary set of functions for serializing and deserializing extensions to be sent with the handshake is also included, implementing the protocol in proposal 332 § A.2. Currently, it only implements the congestion control extensions specified in proposal 324 § 10.3. part of arti#88 2022-06-24T17:31:38Z Nick Mathewson nickm@torproject.org 2022-06-24T17:31:38Z urn:sha1:1dda69af2b102b72c149503b49f7e598a8f8af5e 2022-06-24T16:00:22Z Nick Mathewson nickm@torproject.org 2022-06-24T16:00:22Z urn:sha1:20435aea751331817709acde8d4b65b5fb8d8f12 These were done with the following commands: ``` cargo set-version -p tor-basic-utils --bump patch cargo set-version -p fs-mistrust --bump minor cargo set-version -p tor-error --bump patch cargo set-version -p tor-config --bump patch cargo set-version -p tor-units --bump patch cargo set-version -p tor-rtcompat --bump minor cargo set-version -p tor-llcrypto --bump patch cargo set-version -p tor-bytes --bump minor cargo set-version -p tor-socksproto --bump minor cargo set-version -p tor-cert --bump minor cargo set-version -p tor-cell --bump minor cargo set-version -p tor-proto --bump minor cargo set-version -p tor-netdoc --bump patch cargo set-version -p tor-netdir --bump minor cargo set-version -p tor-persist --bump patch cargo set-version -p tor-chanmgr --bump minor cargo set-version -p tor-guardmgr --bump minor cargo set-version -p tor-circmgr --bump patch cargo set-version -p tor-dirclient --bump patch cargo set-version -p tor-dirmgr --bump minor cargo set-version -p arti-client --bump patch cargo set-version -p arti --bump minor cargo set-version -p arti-bench --bump minor cargo set-version -p arti-testing --bump minor ``` 2022-06-24T14:13:58Z Ian Jackson iwj@torproject.org 2022-06-24T14:13:58Z urn:sha1:4831f9d38c8b3599184ca5f93a9929f784c8026b Fix clippy nightly again See merge request tpo/core/arti!603 2022-06-24T12:18:15Z Nick Mathewson nickm@torproject.org 2022-06-24T12:18:15Z urn:sha1:ea3160737c8c7737136f29b974f1a72a14b00014 2022-06-23T18:15:42Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-06-23T18:15:29Z urn:sha1:589c6e52bb49ccfe6c0ad9d18d6b994978e46c6c Update all lint blocks 2022-06-22T19:21:12Z Nick Mathewson nickm@torproject.org 2022-06-22T19:11:18Z urn:sha1:0369995364c04f9476dbedd55d50caf915017ea7 2022-06-22T14:02:42Z Nick Mathewson nickm@torproject.org 2022-06-22T14:02:42Z urn:sha1:c3da82fc2d44816a96ac6175a843321199f34af7 2022-06-21T18:14:14Z Nick Mathewson nickm@torproject.org 2022-06-21T18:14:14Z urn:sha1:08d9bbf33b9fff8aa33a823422aa4e323137be07 According to doc/Errors.md, and in keeping with current best practices, we should not include display an error's `source()` as part of that error's display method. Instead, we should let the caller decide to call source() and display that error in turn. Part of #323. 2022-06-10T19:32:21Z Nick Mathewson nickm@torproject.org 2022-06-10T19:26:51Z urn:sha1:8a586a40fa4afbd5402737406b287dc488c6f66a The "full" feature is a catch-all for all features, _except_: * Those that select a particular implementation (like tor-llcrypto/with-openssl) or build flag (like "static") * Those that are experimental or unstable (like "experimental-api") * Those that are testing-only.