summaryrefslogtreecommitdiff
path: root/crates/tor-circmgr/Cargo.toml
Commit message (Collapse)AuthorAgeFilesLines
* Bump tor-netdir and tor-guardmgr versionsarti-v0.0.4Nick Mathewson2022-01-311-4/+4
| | | | | | | | tor-netdir needs to bump because tor-netdoc bumped, even though there were no other changes in tor-netdir. Whoops. tor-guardmgr needs to bump because it already published, with the older tor-netdir.
* Bump the patch version of every crate that changed since 0.0.3Nick Mathewson2022-01-311-10/+10
|
* Make the native-tls crate optional.Nick Mathewson2022-01-261-1/+1
| | | | | | | | | | | 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
* Refactor Runtimes to use separate TLS implementations internally.Nick Mathewson2022-01-191-1/+0
| | | | | This will make it easier to implement them using some other TLS provider as well, without having to duplicate all of our code.
* Bump all crate versions to 0.0.3.Nick Mathewson2022-01-111-17/+17
|
* Minimize the required version for each dependency.Nick Mathewson2022-01-071-12/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Bump every crate by one patch version.Nick Mathewson2021-11-291-17/+17
|
* Move top-level configuration downwards from `arti` to `arti-config`.Nick Mathewson2021-11-181-0/+1
| | | | | | | | To do this at all neatly, I had to split out `tor-config` from `arti-config` again, and putting the lower level stuff (paths, builder errors) into tor-config. I also changed our use of derive_builder to always use a common error type, to avoid error type proliferation.
* Document that the "experimental-api" feature is not semver-covered.Nick Mathewson2021-11-111-0/+4
|
* tor-circmgr: test ExitPathBuilder with guards.Nick Mathewson2021-11-021-0/+1
|
* tor-circmgr: test DirPathBuilder with GuardMgr.Nick Mathewson2021-11-021-0/+1
|
* Bump all crate versions to 0.0.1Nick Mathewson2021-10-291-14/+14
|
* Pass the guard manager down to the path selection functions.Nick Mathewson2021-10-111-0/+1
|
* Add a GuardMgr member to CircuitBuilderNick Mathewson2021-10-101-0/+1
|
* Initial backend implementation for guard node manager.Nick Mathewson2021-10-071-1/+1
| | | | | | | There are some missing parts here (like persistence and tests) and some incorrect parts (I am 90% sure that the "exploratory circuit" flag is bogus). Also it is not integrated with the circuit manager code.
* Move all crates into a `crates` subdirectory.Nick Mathewson2021-08-271-0/+45
This will cause some pain for now, but now is really the best time to do this kind of thing.