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

63 lines
2.3 KiB
TOML
Raw Normal View History

Implement a channel-manager type to get or launch channels on request.
2020-10-29 13:31:34 +00:00
[package]
name = "tor-chanmgr"
Patchlevel bumps for remaining changed crates. These crates have had small code changes, but no API additions: tor-config tor-socksproto tor-cert tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr arti tor-hsservice tor-congestion These crates have had API extensions: fs-mistrust tor-llcrypto tor-bytes tor-checkable tor-linkspec tor-netdoc tor-persist arti-client
2023-02-28 12:13:27 +00:00
version = "0.8.2"
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"
bump rust-version to 1.60 in every crate.
2022-11-07 19:18:02 +00:00
rust-version = "1.60"
Implement a channel-manager type to get or launch channels on request.
2020-10-29 13:31:34 +00: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 = "Manage a set of connections to the Tor network"
Reformat all not-yet-reformatted Cargo.toml files. There are no semantic changes here; only formatting. This is in preparation for other changes (wrt MSRV and edition)
2022-04-25 17:03:41 +01:00
keywords = ["tor", "arti", "async"]
categories = ["network-programming", "cryptography"]
repository = "https://gitlab.torproject.org/tpo/core/arti.git/"
Implement a channel-manager type to get or launch channels on request.
2020-10-29 13:31:34 +00:00
[features]
Mark all bridge and pt features as experimental for now. Also, document the features. Closes #588.
2022-09-29 15:59:19 +01:00
default = []
Mark set-default-factory API as experimental.
2022-11-23 15:52:22 +00:00
experimental = ["experimental-api"]
experimental-api = []
chanmgr: Make "pt-client" non-experimental.
2022-11-16 17:30:08 +00:00
full = ["pt-client"]
chanmgr: Add the code necessary to use SOCKS PTs via a TransportHelper This is mostly a matter of encoding parameters in the format used for socks authentication.
2022-10-18 15:00:57 +01:00
pt-client = ["tor-linkspec/pt-client"]
tor-chanmgr: don't log addresses so much. We now log connection attempts at debug!, and mark relay target addresses as sensitive.
2022-08-25 15:54:50 +01:00
testing = []
Implement a channel-manager type to get or launch channels on request.
2020-10-29 13:31:34 +00: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
async-trait = "0.1.2"
Introduce ChannelConfig This commit is just the necessary plumbing. The config is currently empty. We'll add something to it, for padding control, later.
2022-07-27 20:34:43 +01:00
derive_builder = { version = "0.11.2", package = "derive_builder_fork_arti" }
Require derive_more 0.99.3 0.99.[012] have a bug https://github.com/JelteF/derive_more/issues/114 which makes the Deref derive for bridgedesc::StateGuard not work and therefore breaks minimal-versions CI. It seems simpler to require the newer version everywhere.
2022-11-01 10:59:37 +00:00
derive_more = "0.99.3"
Replace manual Debug impl with educe in tor-chanmgr
2022-03-02 17:10:47 +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"
Upgrade to Postage 0.5.0
2022-04-25 21:06:31 +01:00
postage = { version = "0.5.0", default-features = false, features = ["futures-traits"] }
Expire channels that have been unused for too long
2022-02-04 04:36:01 +00:00
rand = "0.8"
Bump the patch version of every crate that had API additions These crates had API or behavior changes that may affect downstream crates. Fortunately, they're all version 0.x, and don't need minor bumps for this.
2023-02-01 15:36:29 +00:00
safelog = { path = "../safelog", version = "0.2.1" }
Introduce ChannelConfig This commit is just the necessary plumbing. The config is currently empty. We'll add something to it, for padding control, later.
2022-07-27 20:34:43 +01:00
serde = { version = "1.0.103", features = ["derive"] }
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
thiserror = "1"
Bump the minor version of every crate. We made this job easy this time around: by incrementing our MSRV, we have forced ourselves to do at least a minor bump everywhere.
2022-11-30 20:10:16 +00:00
tor-basic-utils = { path = "../tor-basic-utils", version = "0.5.0" }
Bump minor versions for significant breaking changes. This includes tor-cell, tor-proto, and tor-netdir.
2023-02-28 12:05:15 +00:00
tor-cell = { path = "../tor-cell", version = "0.9.0" }
Patchlevel bumps for remaining changed crates. These crates have had small code changes, but no API additions: tor-config tor-socksproto tor-cert tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr arti tor-hsservice tor-congestion These crates have had API extensions: fs-mistrust tor-llcrypto tor-bytes tor-checkable tor-linkspec tor-netdoc tor-persist arti-client
2023-02-28 12:13:27 +00:00
tor-config = { path = "../tor-config", version = "0.7.2" }
Bump the patch version of every crate that had API additions These crates had API or behavior changes that may affect downstream crates. Fortunately, they're all version 0.x, and don't need minor bumps for this.
2023-02-01 15:36:29 +00:00
tor-error = { path = "../tor-error", version = "0.4.1" }
Patchlevel bumps for remaining changed crates. These crates have had small code changes, but no API additions: tor-config tor-socksproto tor-cert tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr arti tor-hsservice tor-congestion These crates have had API extensions: fs-mistrust tor-llcrypto tor-bytes tor-checkable tor-linkspec tor-netdoc tor-persist arti-client
2023-02-28 12:13:27 +00:00
tor-linkspec = { path = "../tor-linkspec", version = "0.6.2" }
tor-llcrypto = { path = "../tor-llcrypto", version = "0.4.2" }
Bump minor versions for significant breaking changes. This includes tor-cell, tor-proto, and tor-netdir.
2023-02-28 12:05:15 +00:00
tor-netdir = { path = "../tor-netdir", version = "0.8.0" }
tor-proto = { path = "../tor-proto", version = "0.9.0" }
Bump the patch-level version of crates with _minor_ changes. These changes influence behavior, but not effect compatibility. (If I messed up, and any crate except for `arti` has non-breaking API changes, that's still fine, since they are all version 0.x.)
2023-02-01 15:23:58 +00:00
tor-rtcompat = { path = "../tor-rtcompat", version = "0.8.1" }
Patchlevel bumps for remaining changed crates. These crates have had small code changes, but no API additions: tor-config tor-socksproto tor-cert tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr arti tor-hsservice tor-congestion These crates have had API extensions: fs-mistrust tor-llcrypto tor-bytes tor-checkable tor-linkspec tor-netdoc tor-persist arti-client
2023-02-28 12:13:27 +00:00
tor-socksproto = { path = "../tor-socksproto", version = "0.6.2", default-features = false, features = [
chanmgr: Begin a socks-client implementation. This code is _not_ conditional, since we want to support running with a proxy even if we don't support pluggable transports. We may eventually want to refactor this into a new create.
2022-10-17 14:49:32 +01:00
"client-handshake",
] }
Bump tor-units version for breaking change. (The breaking change was removing `as_days()` from IntegerMinutes.) We are _not_ calling this a downstream-api breaking change, per discussion at https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1012?commit_id=bb2ab7c2a3e0994bb438188511688b5b039cae29#note_2876819
2023-02-28 12:10:00 +00:00
tor-units = { path = "../tor-units", 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
tracing = "0.1.18"
tor-chanmgr: Change to use unwrap_void As per discussion in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/586#note_2813573
2022-06-21 19:13:13 +01:00
void = "1"
Tests for tor-chanmgr.
2020-10-30 19:45:53 +00:00
[dev-dependencies]
Upgrade float_eq dev-dependency to 1.0.0
2022-06-07 13:03:55 +01:00
float_eq = "1.0.0"
Tests for tor-chanmgr.
2020-10-30 19:45:53 +00:00
futures-await-test = "0.3.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
hex-literal = "0.3"
channel padding: Test through most of the layers
2022-07-22 18:14:05 +01:00
itertools = "0.10.1"
Bump minor versions for significant breaking changes. This includes tor-cell, tor-proto, and tor-netdir.
2023-02-28 12:05:15 +00:00
tor-cell = { path = "../tor-cell", version = "0.9.0", features = ["testing"] }
tor-netdir = { path = "../tor-netdir", version = "0.8.0", features = ["testing"] }
tor-proto = { path = "../tor-proto", version = "0.9.0", features = ["testing"] }
Bump the patch-level version of crates with _minor_ changes. These changes influence behavior, but not effect compatibility. (If I messed up, and any crate except for `arti` has non-breaking API changes, that's still fine, since they are all version 0.x.)
2023-02-01 15:23:58 +00:00
tor-rtcompat = { path = "../tor-rtcompat", version = "0.8.1", features = ["tokio", "native-tls"] }
Bump the minor version of every crate. We made this job easy this time around: by incrementing our MSRV, we have forced ourselves to do at least a minor bump everywhere.
2022-11-30 20:10:16 +00:00
tor-rtmock = { path = "../tor-rtmock", version = "0.7.0" }
enable doc_auto_cfg feature on every crate when documenting for docs.rs
2022-08-17 20:13:13 +01:00
[package.metadata.docs.rs]
all-features = true
rustdoc-args = ["--cfg", "docsrs"]