vincenzopalazzo
/
arti
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
arti/crates/tor-proto/Cargo.toml

70 lines
2.4 KiB
TOML
Raw Normal View History

Fresh git repository for work on "arti" Arti is a rust tor implementation. It's project I've been working on for a few months now, in weekends and in spare time. It doesn't speak the tor protocol yet, and it doesn't connect to the network at all. It needs much more documentation and testing, but I'm just about ready to show it to others. See the README.md for a description of what is there and what isn't.
2020-05-08 00:58:10 +01:00
[package]
name = "tor-proto"
Bump minor version on crates with deps with breaking changes. This performs the transitive closure of the last operation: everything that depends on a crate with a breaking change gets the version which it depends on bumped. ``` cargo set-version -p tor-proto --bump minor cargo set-version -p tor-netdoc --bump minor cargo set-version -p arti-hyper --bump minor cargo set-version -p arti-bench --bump minor cargo set-version -p arti-testing --bump minor cargo set-version -p tor-config --bump minor ```
2022-08-01 14:47:52 +01:00
version = "0.5.0"
Add the tor project as an author.
2021-03-17 18:43:40 +00:00
authors = ["The Tor Project, Inc.", "Nick Mathewson <nickm@torproject.org>"]
Bump every crate's edition to 2021. This is an automated change made with a perl one-liner and verified with grep -L and grep -l. Some warnings are introduced with this change; they will be removed in subsequent commits. See arti#208 for older discussion on this issue.
2022-04-25 17:19:02 +01:00
edition = "2021"
Add 'rust-version = "1.56"' to every Cargo.toml file. This change was made automatically with a perl one-liner, and confirmed with `grep -L`. The `rust-version` field itself was introduced in 1.56.0.
2022-04-25 17:10:41 +01:00
rust-version = "1.56"
Fresh git repository for work on "arti" Arti is a rust tor implementation. It's project I've been working on for a few months now, in weekends and in spare time. It doesn't speak the tor protocol yet, and it doesn't connect to the network at all. It needs much more documentation and testing, but I'm just about ready to show it to others. See the README.md for a description of what is there and what isn't.
2020-05-08 00:58:10 +01:00
license = "MIT OR Apache-2.0"
Give it a homepage everyplace.
2021-03-17 18:13:26 +00:00
homepage = "https://gitlab.torproject.org/tpo/core/arti/-/wikis/home"
Add a description field to all our Cargo.toml files
2021-03-17 18:31:59 +00:00
description = "Asynchronous client-side implementation of the central Tor network protocols"
Upgrade to digest v0.10.0 We generally try to track the latest rust-crypto traits when we can: fortunately, this upgrade didn't break much, considering.
2021-12-08 01:33:46 +00:00
keywords = ["tor", "arti", "networking", "anonymity"]
categories = ["network-programming", "cryptography"]
repository = "https://gitlab.torproject.org/tpo/core/arti.git/"
Fresh git repository for work on "arti" Arti is a rust tor implementation. It's project I've been working on for a few months now, in weekends and in spare time. It doesn't speak the tor protocol yet, and it doesn't connect to the network at all. It needs much more documentation and testing, but I'm just about ready to show it to others. See the README.md for a description of what is there and what isn't.
2020-05-08 00:58:10 +01:00
hs_ntor: add a disclaimer and put it behind a feature.
2021-04-02 13:34:03 +01:00
[features]
default = []
Add "full" and "experimental" features to arti-client and below. 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.
2022-06-10 20:26:51 +01:00
full = ["tokio"]
experimental = ["hs", "ntor_v3"]
hs_ntor: add a disclaimer and put it behind a feature.
2021-04-02 13:34:03 +01:00
hs = []
Basic implementation for prop#332 ntor v3 backend. This isn't tied into the protocol code yet, since we don't actually have anybody to negotiate with here. We'll need some API tweaks in order to express the sending of extended information too. For now, I'm putting it behind a feature, but if we build this into the tor network, the feature-gate should go away.
2021-08-20 14:42:30 +01:00
ntor_v3 = []
tor-proto: Make "testing" feature that exports some things We are going to want this for through-the-layers padding control testing.
2022-07-22 17:38:37 +01:00
# Enable testing-only APIs. APIs under this feature are not
# covered by semver.
testing = []
Upgrade to digest v0.10.0 We generally try to track the latest rust-crypto traits when we can: fortunately, this upgrade didn't break much, considering.
2021-12-08 01:33:46 +00:00
tokio = ["tokio-crate", "tokio-util"]
hs_ntor: add a disclaimer and put it behind a feature.
2021-04-02 13:34:03 +01:00
Fresh git repository for work on "arti" Arti is a rust tor implementation. It's project I've been working on for a few months now, in weekends and in spare time. It doesn't speak the tor protocol yet, and it doesn't connect to the network at all. It needs much more documentation and testing, but I'm just about ready to show it to others. See the README.md for a description of what is there and what isn't.
2020-05-08 00:58:10 +01:00
[dependencies]
Minimize the required version for each dependency. I found these versions empirically, by using the following process: First, I used `cargo tree --depth 1 --kind all` to get a list of every immediate dependency we had. Then, I used `cargo upgrade --workspace package@version` to change each dependency to the earliest version with which (in theory) the current version is semver-compatible. IOW, if the current version was 3.2.3, I picked "3". If the current version was 0.12.8, I picked "0.12". Then, I used `cargo +nightly upgrade -Z minimal-versions` to downgrade Cargo.lock to the minimal listed version for each dependency. (I had to override a few packages; see .gitlab-ci.yml for details). Finally, I repeatedly increased the version of each of our dependencies until our code compiled and the tests passed. Here's what I found that we need: anyhow >= 1.0.5: Earlier versions break our hyper example. async-broadcast >= 0.3.2: Earlier versions fail our tests. async-compression 0.3.5: Earlier versions handled futures and tokio differently. async-trait >= 0.1.2: Earlier versions are too buggy to compile our code. clap 2.33.0: For Arg::default_value_os(). coarsetime >= 0.1.20: exposed as_ticks() function. curve25519-dalek >= 3.2: For is_identity(). generic-array 0.14.3: Earlier versions don't implement From<&[T; 32]> httparse >= 1.2: Earlier versions didn't implement Error. itertools at 0.10.1: For at_most_once. rusqlite >= 0.26.3: for backward compatibility with older rustc. serde 1.0.103: Older versions break our code. serde_json >= 1.0.50: Since we need its Value type to implement Eq. shellexpand >= 2.1: To avoid a broken dirs crate version. tokio >= 1.4: For Handle::block_on(). tracing >= 0.1.18: Previously, tracing_core and tracing had separate LevelFilter types. typenum >= 1.12: Compatibility with rust-crypto crates x25519-dalek >= 1.2.0: For was_contributory(). Closes #275.
2022-01-07 20:54:24 +00:00
arrayref = "0.3"
Lexically sort Cargo.toml dependencies Utilize cargo-sort: https://github.com/DevinR528/cargo-sort Signed-off-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2022-05-28 17:41:39 +01:00
asynchronous-codec = "0.6.0"
Minimize the required version for each dependency. I found these versions empirically, by using the following process: First, I used `cargo tree --depth 1 --kind all` to get a list of every immediate dependency we had. Then, I used `cargo upgrade --workspace package@version` to change each dependency to the earliest version with which (in theory) the current version is semver-compatible. IOW, if the current version was 3.2.3, I picked "3". If the current version was 0.12.8, I picked "0.12". Then, I used `cargo +nightly upgrade -Z minimal-versions` to downgrade Cargo.lock to the minimal listed version for each dependency. (I had to override a few packages; see .gitlab-ci.yml for details). Finally, I repeatedly increased the version of each of our dependencies until our code compiled and the tests passed. Here's what I found that we need: anyhow >= 1.0.5: Earlier versions break our hyper example. async-broadcast >= 0.3.2: Earlier versions fail our tests. async-compression 0.3.5: Earlier versions handled futures and tokio differently. async-trait >= 0.1.2: Earlier versions are too buggy to compile our code. clap 2.33.0: For Arg::default_value_os(). coarsetime >= 0.1.20: exposed as_ticks() function. curve25519-dalek >= 3.2: For is_identity(). generic-array 0.14.3: Earlier versions don't implement From<&[T; 32]> httparse >= 1.2: Earlier versions didn't implement Error. itertools at 0.10.1: For at_most_once. rusqlite >= 0.26.3: for backward compatibility with older rustc. serde 1.0.103: Older versions break our code. serde_json >= 1.0.50: Since we need its Value type to implement Eq. shellexpand >= 2.1: To avoid a broken dirs crate version. tokio >= 1.4: For Handle::block_on(). tracing >= 0.1.18: Previously, tracing_core and tracing had separate LevelFilter types. typenum >= 1.12: Compatibility with rust-crypto crates x25519-dalek >= 1.2.0: For was_contributory(). Closes #275.
2022-01-07 20:54:24 +00:00
bytes = "1"
Use the `zeroize` feature in several crates Using `zeroize` here tells these crates that they should make various structures zeroize-on-drop. (This is not yet implemented in `aes` 0.8.1, but support has been merged in the repository for `aes`, so it should go out in the next release.) No corresponding feature flag is needed to enable zeroize-on-drop for `rsa` and `*25519-dalek` private keys.
2022-08-01 17:13:05 +01:00
cipher = { version = "0.4.1", features = ["zeroize"] }
Make coarsetime dependency and traffic-timestamping non-optional. Previously coarsetime and the traffic-timestamp feature were enabled, since they were only required for a small corner of the guardmgr algorithm. But in 1.0 and beyond we'll be adding a bunch of other features (eg, netflow padding, DoS prevention) that will need coarsetime all over the place. And since we're going to be doing coarsetime all over the place, the previous justification for making traffic-timestamping optional (the tiny performance hit) is no longer relevant.
2022-02-25 15:31:01 +00:00
coarsetime = "0.1.20"
channel padding: Make Parameters a pub struct with builder chanmgr is going to want to make one of these from a NetDir.
2022-06-13 14:33:11 +01:00
derive_builder = { version = "0.11.2", package = "derive_builder_fork_arti" }
Upgrade to digest v0.10.0 We generally try to track the latest rust-crypto traits when we can: fortunately, this upgrade didn't break much, considering.
2021-12-08 01:33:46 +00:00
digest = "0.10.0"
Replace manual Debug impls with educe in tor-proto We now print slighly more information.
2022-03-02 15:44:09 +00:00
educe = "0.4.6"
Upgrade required version of futures crate to 0.3.14 Earlier versions have a bug in UnboundedReceiver that make our new dirclient tests fail.
2022-01-28 19:50:03 +00:00
futures = "0.3.14"
Minimize the required version for each dependency. I found these versions empirically, by using the following process: First, I used `cargo tree --depth 1 --kind all` to get a list of every immediate dependency we had. Then, I used `cargo upgrade --workspace package@version` to change each dependency to the earliest version with which (in theory) the current version is semver-compatible. IOW, if the current version was 3.2.3, I picked "3". If the current version was 0.12.8, I picked "0.12". Then, I used `cargo +nightly upgrade -Z minimal-versions` to downgrade Cargo.lock to the minimal listed version for each dependency. (I had to override a few packages; see .gitlab-ci.yml for details). Finally, I repeatedly increased the version of each of our dependencies until our code compiled and the tests passed. Here's what I found that we need: anyhow >= 1.0.5: Earlier versions break our hyper example. async-broadcast >= 0.3.2: Earlier versions fail our tests. async-compression 0.3.5: Earlier versions handled futures and tokio differently. async-trait >= 0.1.2: Earlier versions are too buggy to compile our code. clap 2.33.0: For Arg::default_value_os(). coarsetime >= 0.1.20: exposed as_ticks() function. curve25519-dalek >= 3.2: For is_identity(). generic-array 0.14.3: Earlier versions don't implement From<&[T; 32]> httparse >= 1.2: Earlier versions didn't implement Error. itertools at 0.10.1: For at_most_once. rusqlite >= 0.26.3: for backward compatibility with older rustc. serde 1.0.103: Older versions break our code. serde_json >= 1.0.50: Since we need its Value type to implement Eq. shellexpand >= 2.1: To avoid a broken dirs crate version. tokio >= 1.4: For Handle::block_on(). tracing >= 0.1.18: Previously, tracing_core and tracing had separate LevelFilter types. typenum >= 1.12: Compatibility with rust-crypto crates x25519-dalek >= 1.2.0: For was_contributory(). Closes #275.
2022-01-07 20:54:24 +00:00
generic-array = "0.14.3"
Upgrade to digest v0.10.0 We generally try to track the latest rust-crypto traits when we can: fortunately, this upgrade didn't break much, considering.
2021-12-08 01:33:46 +00:00
hkdf = "0.12.0"
hmac = "0.12.0"
tor-proto: channel: Provide padding::Timer
2022-06-06 18:39:49 +01:00
pin-project = "1"
Minimize the required version for each dependency. I found these versions empirically, by using the following process: First, I used `cargo tree --depth 1 --kind all` to get a list of every immediate dependency we had. Then, I used `cargo upgrade --workspace package@version` to change each dependency to the earliest version with which (in theory) the current version is semver-compatible. IOW, if the current version was 3.2.3, I picked "3". If the current version was 0.12.8, I picked "0.12". Then, I used `cargo +nightly upgrade -Z minimal-versions` to downgrade Cargo.lock to the minimal listed version for each dependency. (I had to override a few packages; see .gitlab-ci.yml for details). Finally, I repeatedly increased the version of each of our dependencies until our code compiled and the tests passed. Here's what I found that we need: anyhow >= 1.0.5: Earlier versions break our hyper example. async-broadcast >= 0.3.2: Earlier versions fail our tests. async-compression 0.3.5: Earlier versions handled futures and tokio differently. async-trait >= 0.1.2: Earlier versions are too buggy to compile our code. clap 2.33.0: For Arg::default_value_os(). coarsetime >= 0.1.20: exposed as_ticks() function. curve25519-dalek >= 3.2: For is_identity(). generic-array 0.14.3: Earlier versions don't implement From<&[T; 32]> httparse >= 1.2: Earlier versions didn't implement Error. itertools at 0.10.1: For at_most_once. rusqlite >= 0.26.3: for backward compatibility with older rustc. serde 1.0.103: Older versions break our code. serde_json >= 1.0.50: Since we need its Value type to implement Eq. shellexpand >= 2.1: To avoid a broken dirs crate version. tokio >= 1.4: For Handle::block_on(). tracing >= 0.1.18: Previously, tracing_core and tracing had separate LevelFilter types. typenum >= 1.12: Compatibility with rust-crypto crates x25519-dalek >= 1.2.0: For was_contributory(). Closes #275.
2022-01-07 20:54:24 +00:00
rand = "0.8"
Add a compatibility layer so we can upgrade rand_core. dalek-crypto is stuck on rand_core 0.5.1, so we've been stuck too. This commit introduces a compatibility module so that we can wrap new rand_core instances to make them backward compatible.
2021-03-18 17:14:53 +00:00
rand_core = "0.6.2"
Minimize the required version for each dependency. I found these versions empirically, by using the following process: First, I used `cargo tree --depth 1 --kind all` to get a list of every immediate dependency we had. Then, I used `cargo upgrade --workspace package@version` to change each dependency to the earliest version with which (in theory) the current version is semver-compatible. IOW, if the current version was 3.2.3, I picked "3". If the current version was 0.12.8, I picked "0.12". Then, I used `cargo +nightly upgrade -Z minimal-versions` to downgrade Cargo.lock to the minimal listed version for each dependency. (I had to override a few packages; see .gitlab-ci.yml for details). Finally, I repeatedly increased the version of each of our dependencies until our code compiled and the tests passed. Here's what I found that we need: anyhow >= 1.0.5: Earlier versions break our hyper example. async-broadcast >= 0.3.2: Earlier versions fail our tests. async-compression 0.3.5: Earlier versions handled futures and tokio differently. async-trait >= 0.1.2: Earlier versions are too buggy to compile our code. clap 2.33.0: For Arg::default_value_os(). coarsetime >= 0.1.20: exposed as_ticks() function. curve25519-dalek >= 3.2: For is_identity(). generic-array 0.14.3: Earlier versions don't implement From<&[T; 32]> httparse >= 1.2: Earlier versions didn't implement Error. itertools at 0.10.1: For at_most_once. rusqlite >= 0.26.3: for backward compatibility with older rustc. serde 1.0.103: Older versions break our code. serde_json >= 1.0.50: Since we need its Value type to implement Eq. shellexpand >= 2.1: To avoid a broken dirs crate version. tokio >= 1.4: For Handle::block_on(). tracing >= 0.1.18: Previously, tracing_core and tracing had separate LevelFilter types. typenum >= 1.12: Compatibility with rust-crypto crates x25519-dalek >= 1.2.0: For was_contributory(). Closes #275.
2022-01-07 20:54:24 +00:00
subtle = "2"
thiserror = "1"
Bump minimum tokio to 1.7, since tokio-util now needs that.
2022-02-25 15:56:48 +00:00
tokio-crate = { package = "tokio", version = "1.7", optional = true }
Upgrade dependency to new version of tokio-util.
2022-02-25 13:48:00 +00:00
tokio-util = { version = "0.7.0", features = ["compat"], optional = true }
Bump patch versions on crates that have new APIs. Do _not_ bump the dependency versions on crates that have had no changes since arti 0.0.5, since those crates do not depend on the new APIs. ``` cargo set-version -p tor-basic-utils --bump patch cargo set-version -p tor-llcrypto --bump patch git restore crates/tor-checkable git restore crates/tor-consdiff git restore crates/tor-rtmock ```
2022-08-01 14:56:29 +01:00
tor-basic-utils = { path = "../tor-basic-utils", version = "0.3.3" }
Bump minor versions on all crates that have had breaking changes. Done with these commands: ``` cargo set-version -p fs-mistrust --bump minor 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-linkspec --bump minor cargo set-version -p tor-cell --bump minor cargo set-version -p tor-netdir --bump minor cargo set-version -p tor-persist --bump minor cargo set-version -p tor-chanmgr --bump minor cargo set-version -p tor-guardmgr --bump minor cargo set-version -p tor-circmgr --bump minor cargo set-version -p tor-dirclient --bump minor cargo set-version -p tor-dirmgr --bump minor cargo set-version -p arti-client --bump minor cargo set-version -p arti --bump minor ```
2022-08-01 14:43:09 +01:00
tor-bytes = { path = "../tor-bytes", version = "0.5.0" }
tor-cell = { path = "../tor-cell", version = "0.5.0" }
tor-cert = { path = "../tor-cert", version = "0.5.0" }
Lexically sort Cargo.toml dependencies Utilize cargo-sort: https://github.com/DevinR528/cargo-sort Signed-off-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2022-05-28 17:41:39 +01:00
tor-checkable = { path = "../tor-checkable", version = "0.3.0" }
tor-proto: padding::Parameters: use impl_standard_builder This is more standard. It also provides the ::build() method. This isn't a config type, and build failures ought not to happen, so we use Bug for the error.
2022-07-25 14:53:26 +01:00
tor-config = { path = "../tor-config", version = "0.5.0" }
Bump crate and dependency versions. 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-24 17:00:22 +01:00
tor-error = { path = "../tor-error", version = "0.3.2" }
Bump minor versions on all crates that have had breaking changes. Done with these commands: ``` cargo set-version -p fs-mistrust --bump minor 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-linkspec --bump minor cargo set-version -p tor-cell --bump minor cargo set-version -p tor-netdir --bump minor cargo set-version -p tor-persist --bump minor cargo set-version -p tor-chanmgr --bump minor cargo set-version -p tor-guardmgr --bump minor cargo set-version -p tor-circmgr --bump minor cargo set-version -p tor-dirclient --bump minor cargo set-version -p tor-dirmgr --bump minor cargo set-version -p arti-client --bump minor cargo set-version -p arti --bump minor ```
2022-08-01 14:43:09 +01:00
tor-linkspec = { path = "../tor-linkspec", version = "0.4.0" }
Bump patch versions on crates that have new APIs. Do _not_ bump the dependency versions on crates that have had no changes since arti 0.0.5, since those crates do not depend on the new APIs. ``` cargo set-version -p tor-basic-utils --bump patch cargo set-version -p tor-llcrypto --bump patch git restore crates/tor-checkable git restore crates/tor-consdiff git restore crates/tor-rtmock ```
2022-08-01 14:56:29 +01:00
tor-llcrypto = { path = "../tor-llcrypto", version = "0.3.3" }
Lexically sort Cargo.toml dependencies Utilize cargo-sort: https://github.com/DevinR528/cargo-sort Signed-off-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2022-05-28 17:41:39 +01:00
tor-protover = { path = "../tor-protover", version = "0.3.0" }
Bump crate and dependency versions. 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-24 17:00:22 +01:00
tor-rtcompat = { path = "../tor-rtcompat", version = "0.5.0" }
tor-proto: channel: Provide padding::Timer
2022-06-06 18:39:49 +01:00
tor-rtmock = { path = "../tor-rtmock", version = "0.4.0" }
Bump crate and dependency versions. 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-24 17:00:22 +01:00
tor-units = { path = "../tor-units", version = "0.3.1" }
Lexically sort Cargo.toml dependencies Utilize cargo-sort: https://github.com/DevinR528/cargo-sort Signed-off-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2022-05-28 17:41:39 +01:00
tracing = "0.1.18"
typenum = "1.12"
zeroize = "1"
tor-proto: implement tokio Async{Read, Write} traits conditionally futures::io::AsyncRead (and Write) isn't the same thing as tokio::io::AsyncRead, which is a somewhat annoying misfeature of the Rust async ecosystem (!). To mitigate this somewhat for people trying to use the `DataStream` struct with tokio, implement the tokio versions of the above traits using `tokio-util`'s compat layer, if a crate feature (`tokio`) is enabled.
2021-10-19 17:26:52 +01:00
Fresh git repository for work on "arti" Arti is a rust tor implementation. It's project I've been working on for a few months now, in weekends and in spare time. It doesn't speak the tor protocol yet, and it doesn't connect to the network at all. It needs much more documentation and testing, but I'm just about ready to show it to others. See the README.md for a description of what is there and what isn't.
2020-05-08 00:58:10 +01:00
[dev-dependencies]
Minimize the required version for each dependency. I found these versions empirically, by using the following process: First, I used `cargo tree --depth 1 --kind all` to get a list of every immediate dependency we had. Then, I used `cargo upgrade --workspace package@version` to change each dependency to the earliest version with which (in theory) the current version is semver-compatible. IOW, if the current version was 3.2.3, I picked "3". If the current version was 0.12.8, I picked "0.12". Then, I used `cargo +nightly upgrade -Z minimal-versions` to downgrade Cargo.lock to the minimal listed version for each dependency. (I had to override a few packages; see .gitlab-ci.yml for details). Finally, I repeatedly increased the version of each of our dependencies until our code compiled and the tests passed. Here's what I found that we need: anyhow >= 1.0.5: Earlier versions break our hyper example. async-broadcast >= 0.3.2: Earlier versions fail our tests. async-compression 0.3.5: Earlier versions handled futures and tokio differently. async-trait >= 0.1.2: Earlier versions are too buggy to compile our code. clap 2.33.0: For Arg::default_value_os(). coarsetime >= 0.1.20: exposed as_ticks() function. curve25519-dalek >= 3.2: For is_identity(). generic-array 0.14.3: Earlier versions don't implement From<&[T; 32]> httparse >= 1.2: Earlier versions didn't implement Error. itertools at 0.10.1: For at_most_once. rusqlite >= 0.26.3: for backward compatibility with older rustc. serde 1.0.103: Older versions break our code. serde_json >= 1.0.50: Since we need its Value type to implement Eq. shellexpand >= 2.1: To avoid a broken dirs crate version. tokio >= 1.4: For Handle::block_on(). tracing >= 0.1.18: Previously, tracing_core and tracing had separate LevelFilter types. typenum >= 1.12: Compatibility with rust-crypto crates x25519-dalek >= 1.2.0: For was_contributory(). Closes #275.
2022-01-07 20:54:24 +00:00
hex = "0.4"
Lexically sort Cargo.toml dependencies Utilize cargo-sort: https://github.com/DevinR528/cargo-sort Signed-off-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2022-05-28 17:41:39 +01:00
hex-literal = "0.3"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
itertools = "0.10.1"
tor-proto: Unify the check_match code in channel and handshake This had to become a new internal function, since at the point that the handshake needs this code, it does not yet have a Channel to use. This change made the error messages in the handshake code more informative: and now they require a regex to check. Later, we might want to defer formatting these strings, but I don't think we need to do it now.
2022-08-09 21:19:48 +01:00
regex = { version = "1", default-features = false, features = ["std"] }
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
statrs = "0.15.0"
tor-proto: channel: Provide padding::Timer
2022-06-06 18:39:49 +01:00
tokio-crate = { package = "tokio", version = "1.7", features = ["full"] }
Bump crate and dependency versions. 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-24 17:00:22 +01:00
tor-rtcompat = { path = "../tor-rtcompat", version = "0.5.0", features = ["tokio", "native-tls"] }