vincenzopalazzo
/
arti
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
arti/Cargo.lock

5598 lines
125 KiB
Plaintext
Raw Normal View History

make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
version = 3
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
[[package]]
name = "addr2line"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "0.19.0"
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "a76fd60b23679b7d19bd066031410fb7e458ccc5e958eb5c325888ce4baedc97"
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
dependencies = [
"gimli",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "adler"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe"
[[package]]
name = "aes"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.8.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "ac1f845298e95f983ff1944b728ae08b8cebab80d684f0a832ed0fc74dfa27e2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"cipher",
"cpufeatures",
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
"zeroize",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "ahash"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.8.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "2c99f64d1e06488f620f932677e24bc6e2897582980441ae90a671415bd7ec2f"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update".
2023-05-22 12:47:20 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"once_cell",
"version_check",
]
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
[[package]]
name = "aho-corasick"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "1.0.2"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "43f6cb1bf222025340178f382c426f13757b2960e89779dfcb319c32542a5a41"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
dependencies = [
"memchr",
]
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
[[package]]
name = "allocator-api2"
version = "0.2.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "56fc6cf8dc8c4158eed8649f9b8b0ea1518eb62b544fe9490d66fa0b349eafe9"
netdoc: Use derive amplify::Getters for HsDesc accessors. Closes #909.
2023-06-20 19:00:41 +01:00
[[package]]
name = "amplify"
version = "4.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f26966af46e0d200e8bf2b7f16230997c1c3f2d141bc27ccc091c012ed527b58"
dependencies = [
"amplify_derive",
"amplify_num",
"ascii",
"wasm-bindgen",
]
[[package]]
name = "amplify_derive"
version = "3.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c87df0f28e6eb1f2d355f29ba6793fa9ca643967528609608d5cbd70bd68f9d1"
dependencies = [
"amplify_syn",
"proc-macro2",
"quote",
"syn 1.0.109",
]
[[package]]
name = "amplify_num"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ddce3bc63e807ea02065e8d8b702695f3d302ae4158baddff8b0ce5c73947251"
[[package]]
name = "amplify_syn"
version = "2.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7736fb8d473c0d83098b5bac44df6a561e20470375cd8bcae30516dc889fd62a"
dependencies = [
"proc-macro2",
"quote",
"syn 1.0.109",
]
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
[[package]]
name = "android-tzdata"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e999941b234f3131b00bc13c22d06e8c5ff726d1b6318ac7eb276997bbb4fef0"
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
[[package]]
name = "android_system_properties"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "819e7219dbd41043ac279b19830f2efc897156490d7fd6ea916720117ee66311"
dependencies = [
"libc",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
name = "anyhow"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "1.0.71"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "9c7d0618f0e0b7e8ff11427422b64564d5fb0be1940354bfe2e0529b18a9d9b8"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
[[package]]
name = "approx"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cab112f0a86d568ea0e627cc1d6be74a1e9cd55214684db5561995f6dad897c6"
dependencies = [
"num-traits",
]
Fuzzer code for socks client implementation.
2022-09-27 22:16:14 +01:00
[[package]]
name = "arbitrary"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "1.3.0"
Fuzzer code for socks client implementation.
2022-09-27 22:16:14 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "e2d098ff73c1ca148721f37baad5ea6a465a13f9573aba8641fbbbae8164a54e"
Fuzzer code for socks client implementation.
2022-09-27 22:16:14 +01:00
dependencies = [
"derive_arbitrary",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "arti"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "1.1.6"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"anyhow",
Rename tor_client/arti_tor_client to arti_client. Solves a name conflict with the existing tor_client create. Closes #130.
2021-10-21 19:15:13 +01:00
"arti-client",
rpc: Add a demonstration feature to "arti" It's experimental, and tokio-only. To enable it, build with the "rpc" feature turned on, and connect to `~/.arti-rpc-TESTING/PIPE`. (`nc -U` worked for me) I'll add some instructions.
2023-04-05 18:17:30 +01:00
"arti-rpcserver",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"async-ctrlc",
arti: Install a panic hook that sends messages to `tracing` (Also leaves installed the default handler that sends messages to stderr.) Closes #921.
2023-07-05 21:11:04 +01:00
"backtrace",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
"clap",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"config",
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
"derive_builder_fork_arti",
arti cfg tests: Overhaul exception handling This was super confusing and fragile. Amongst the problems: * Information about exceptional config keys was spread across a number of places, manipulated in ad-hoc ways (conditional Vec appends, etc). * As a consequence, each exceptional table has confusing and unclear semantics. * It doesn't deal well with the way that cargo sometimes enables features for dependency crates even if arti itself wouldn't demand them; this can lead to sub-crates supporting config keys when the tests in arti don't expect them to, causing spurious test failures. Fix this: * Introduce a new, systematic, way of writing information about configuration keys that need some kind of special handling. * Use this new approach in *both* sets of "thorough" config tests. * Be more relaxed about deprecated keys. We don't want to tightly couple this to absence in the supported file, I think. * Understand more clearly the concept of keys of which we don't know, in the current build config, whether the code is expected to accept them. I have tested this locally with: for p in '-p arti' '--workspace'; do for f in '--no-default-features --features=tokio,native-tls' '--all-features' ''; do nailing-cargo test $p $f; done; done
2023-06-27 16:06:33 +01:00
"derive_more",
arti: logging config: Replace a manual Debug impl
2022-06-16 14:53:03 +01:00
"educe",
arti: use fs-mistrust to validate configuration file locations.
2022-05-03 20:49:48 +01:00
"fs-mistrust",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"futures",
arti: Add a `logging.time_granularity` option with 1s default. This lets us provide less information in our logs: in particular, it lets us avoid logging with microsecond precision. Closes #551.
2023-07-05 18:09:20 +01:00
"humantime 2.1.0",
"humantime-serde",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
proxy: Mark ENFILES and EMFILES as survivable. I don't love this approach, but those errors aren't distinguished by ErrorKind, so we have to use libc or winapi, apparently. At least nothing here is unsafe. Addresses part of #188.
2021-10-14 18:12:58 +01:00
"libc",
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
"notify",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"once_cell",
arti: cfg: Rename `*_port` to `*_listen` and change the type This commit largely follows the example for resolve_alternative_specs. The difference is that there are two fields, so we use a macro to avoid recapitulating the field names.
2022-08-24 12:46:19 +01:00
"paste",
arti-example-config.toml: Re-un-comment the example settings in test
2022-05-12 14:48:36 +01:00
"regex",
arti: On startup, increase the NOFILE resource limit. The default soft limit is typically enough for process usage on most Unixes, but OSX has a pretty low default (256), which you can run into easily under heavy usage. With this patch, we're going to aim for as much as 16384, if we're allowed. Fixes part of #188.
2021-10-14 18:25:19 +01:00
"rlimit",
Apply `sensitive` in some info-level log messages. This specifically applies the `sensitive` wrapper in the places where we're logging target addresses at level "info" or higher.
2022-05-03 00:44:12 +01:00
"safelog",
arti: Add support for process hardening This is a compile-time feature with an associated configuration flag, both enabled by default. When it's turned on, hardening prevents the arti process from dumping core or being attached to by low-privileged processes. (This is a defense-in-depth measure, not an absolute way to prevent attacks. For more information, see [`secmem_proc`](https://docs.rs/secmem-proc/0.1.1/secmem_proc/).) Closes #364.
2022-08-08 17:28:52 +01:00
"secmem-proc",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"serde",
arti config: Check that example config is exhaustive This is the final piece of #457.
2022-05-26 15:08:47 +01:00
"serde_json",
fix compilation error with async-std
2022-09-06 20:32:20 +01:00
"signal-hook",
Add functionality to listen for SIGHUPs.
2022-08-25 13:34:41 +01:00
"signal-hook-async-std",
arti: Add a `logging.time_granularity` option with 1s default. This lets us provide less information in our logs: in particular, it lets us avoid logging with microsecond precision. Closes #551.
2023-07-05 18:09:20 +01:00
"thiserror",
"time",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tokio",
RPC: Move the "listen" part of the RPC listener code to `arti`. Now there's a module in `arti` that runs the loop for an RPC listener. The part of the old `listener` module that made the framed connections is now part of the `Session` object. There is now yet another a temporary location for the pipe; we should pick something better. At least now it's configurable.
2023-04-20 18:49:31 +01:00
"tokio-util",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"toml 0.7.5",
Move ArtiConfig to new arti::cfg module Code motion and import fixups.
2022-03-21 10:23:22 +00:00
"tor-config",
Provide error reporter and use it in the arti binary
2022-02-18 11:34:53 +00:00
"tor-error",
arti: Interpret socks request to mean "lookup an RPC session" The actual decoding here is just a placeholder. The important part is that we can get either a (SessionId, StreamId) tuple out of the request, or we treat it as part of an isolation token. This commit has a few TODOs for additional things that we'll need in order to build out our design.
2023-05-31 20:56:02 +01:00
"tor-rpcbase",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-rtcompat",
"tor-socksproto",
"tracing",
Tracing configuration for logfiles, per-target filters Previously we could only configure one global tracing filter that applied to stdout and journald. There was no support for log files, either. This patch fixes both issues, by substantially revising the configuration format: There are now separate filters for each log file, for journald, and for the console log. Because we want to allow multiple logfiles, they have to go into an array in the configuration. The configuration logic has grown a bit complicated in its types, since the tracing_subscriber crate would prefer to have the complete structure of tracing Layers known statically. That's fine when you know how many you have, and which kinds there will be, but for the runtime-configuration case we need to mess around with `Box<dyn Layer ...>`. I also had to switch from tracing_subscriber's EnvFilter to its Targets filter. It seems "EnvFilter" can only be applied as a Layer in itself, and won't work as a Filter on an individual Layer. Closes #166. Closes #170.
2022-01-07 15:52:43 +00:00
"tracing-appender",
update misc/Cargo.lock
2021-09-12 09:28:00 +01:00
"tracing-journald",
Remove usage of tracing-test 0.1 It requires tracing-subscriber 0.2, which is a lower version than we want, and which causes trouble with our minimal-versions CI test. There is a pending issue to fix this; we can reinstate tracing-test once it is merged: https://github.com/dbrgn/tracing-test/pull/11
2021-11-11 15:58:25 +00:00
"tracing-subscriber",
actually add DNS support
2022-03-06 19:44:50 +00:00
"trust-dns-proto",
arti: Move most public APIs behind `experimental-api`. The remaining unconditionally public APIs are those related to our configuration objects, and the main_main() API. The rationale for making main_main() public is to have an actual entry point. The rationale for making the config APIs public is: 1. We really do intend for others to be able to read our configuration files using this API. 2. The structure of our configuration files is already part of our interface. Closes #530.
2022-08-08 15:14:30 +01:00
"visibility",
update to v5.0.0
2022-08-12 19:50:08 +01:00
"winapi",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
[[package]]
name = "arti-bench"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.8.6"
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
dependencies = [
"anyhow",
Move ArtiConfig to new arti::cfg module Code motion and import fixups.
2022-03-21 10:23:22 +00:00
"arti",
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
"arti-client",
"clap",
arti-bench: add support for multiple samples & averaging We now do multiple samples (configurable; default 3) per type of `arti-bench` benchmark run, and take a mean and median average of all data collected, in order to hopefully be a bit more resilient to random outliers / variation. This uses some `futures::stream::Stream` hacks, which might result in more connections being made than required (and might impact the TTFB metrics somewhat, at least for downloading). Results now get collected into a `BenchmarkResults` struct per type of benchmark, which will be in turn placed into a `BenchmarkSummary` in a later commit; this will also add the ability to serialize the latter struct out to disk, for future reference. part of arti#292
2022-01-13 16:23:11 +00:00
"float-ord",
arti-bench: Disable all fs permissions (fs-mistrust) checks This is a benchmarking tool, and fs-mistrust doesn't like the permissions in our CI. The env var ARTI_FS_DISABLE_PERMISSION_CHECKS is (of course) specific to arti. Maybe it should be honoured here, or this should be done via the config files. But disabling this is fine for now.
2022-05-12 16:36:28 +01:00
"fs-mistrust",
arti-bench: add support for multiple samples & averaging We now do multiple samples (configurable; default 3) per type of `arti-bench` benchmark run, and take a mean and median average of all data collected, in order to hopefully be a bit more resilient to random outliers / variation. This uses some `futures::stream::Stream` hacks, which might result in more connections being made than required (and might impact the TTFB metrics somewhat, at least for downloading). Results now get collected into a `BenchmarkResults` struct per type of benchmark, which will be in turn placed into a `BenchmarkSummary` in a later commit; this will also add the ability to serialize the latter struct out to disk, for future reference. part of arti#292
2022-01-13 16:23:11 +00:00
"futures",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
"serde",
"serde_json",
"tokio",
"tokio-socks",
arti-config abolition: Change references to use tor_config Generally, change the paths that mention the crate name to go via a module-level "use". This involves adding tor-config as a direct dependency for a few crates.
2022-05-13 11:36:28 +01:00
"tor-config",
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
"tor-rtcompat",
"tracing",
"tracing-subscriber",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
Rename tor_client/arti_tor_client to arti_client. Solves a name conflict with the existing tor_client create. Closes #130.
2021-10-21 19:15:13 +01:00
name = "arti-client"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.9.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
"anyhow",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
"derive_builder_fork_arti",
Implement the basics of a bootstrap-status API. The purpose of a this API is to tell the user how far along Arti is in getting bootstrapped, and if it's stuck, what it's stuck on. This API doesn't yet expose any useful information: by the time it's observable to a client, it's always "100% bootstrapped." But I'm putting it in a MR now so that we can review the basic idea, and to avoid conflicts with later work on tickets like #293 and #278. This is part of #96.
2022-01-12 17:46:26 +00:00
"derive_more",
Remove dependency from arti-client to tor-config. I'm about to make tor-config a higher-level module, so it can't be a dependency for tor-config.
2021-11-16 21:01:55 +00:00
"directories",
Replace manual Debug impl with educe in arti-client
2022-03-02 15:31:36 +00:00
"educe",
arti-client: Configure and use fs-mistrust. This is derived from the environment, not the configuration file: We might not want to trust the configuration file until we've decided whether we like its permissions.
2022-05-03 19:58:03 +01:00
"fs-mistrust",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"futures",
Use hostname-validator crate for hostname validation
2022-09-22 14:48:51 +01:00
"hostname-validator",
Make DNS fields in arti-client/src/client.rs configurable
2021-12-03 18:28:42 +00:00
"humantime-serde",
arti_client: Refuse to build a client if we are setuid. Arti is not designed to be a setuid-safe program. Part of #523.
2022-08-24 14:17:12 +01:00
"libc",
arti-client: add ability to automatically bootstrap The new `BootstrapBehavior` enum controls whether an unbootstrapped `TorClient` will bootstrap itself automatically (`Ondemand`) when an attempt is made to use it, or whether the user must perform bootstrapping themselves (`Manual`). The `lazy-init` example shows how you could write a simple `get_tor_client()` function that used a global `OnceCell` to share a Tor client across an entire application with this API. closes arti#278
2022-02-16 15:57:24 +00:00
"once_cell",
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
"pin-project",
Implement the basics of a bootstrap-status API. The purpose of a this API is to tell the user how far along Arti is in getting bootstrapped, and if it's stuck, what it's stuck on. This API doesn't yet expose any useful information: by the time it's observable to a client, it's always "100% bootstrapped." But I'm putting it in a MR now so that we can review the basic idea, and to avoid conflicts with later work on tickets like #293 and #278. This is part of #96.
2022-01-12 17:46:26 +00:00
"postage",
Apply `sensitive` in some info-level log messages. This specifically applies the `sensitive` wrapper in the places where we're logging target addresses at level "info" or higher.
2022-05-03 00:44:12 +01:00
"safelog",
Introduce ClientConfig for is_localhost config parameter
2021-10-05 23:30:00 +01:00
"serde",
arti-client: Provide ErrorDetailDiscriminants for convenient testing ErrorDetail isn't PartialEq so we can't assert_eq! it. But the discriminants will be.
2023-06-16 14:49:27 +01:00
"strum",
Allow creating unbootstrapped `TorClient`s (and `DirMgr`s) This commit changes how the `TorClient` type works, enabling it to be constructed synchronously without initiating the bootstrapping process. Daemon tasks are still started on construction (although some of them won't do anything if the client isn't bootstrapped). The old bootstrap() methods are now reimplemented in terms of the new create_unbootstrapped() and bootstrap_existing() methods. This required refactoring how the `DirMgr` works to enable the same sort of thing there. closes #293
2022-02-09 16:27:34 +00:00
"tempfile",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"thiserror",
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
"tokio",
"tokio-util",
Move functionality from tor_basic_utils to tor_async_utils This commit is mostly code movement; I'd recommend reviewing it with git's `--color-moved` option.
2023-03-29 14:17:13 +01:00
"tor-async-utils",
Move skip_fmt into tor-basic-utils Code motion and the minimal mechanical changes. As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/375#note_2783078
2022-03-04 11:42:49 +00:00
"tor-basic-utils",
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
"tor-cell",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-chanmgr",
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
"tor-checkable",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-circmgr",
Move top-level configuration downwards from `arti` to `arti-config`. 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.
2021-11-17 19:16:55 +00:00
"tor-config",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-dirmgr",
tor-error: Add as a ddpendency to many crates Doing this here makes it easier when I rebase/reorder things
2022-02-03 19:06:59 +00:00
"tor-error",
Turn FallbackList into a real type, and store one in GuardMgr. The guard manager is responsible for handing out the first hops of tor circuits, keeping track of their successes and failures, and remembering their states. Given that, it makes sense to store this information here. It is not yet used; I'll be fixing that in upcoming commits. Arguably, this information no longer belongs in the directory manager: I've added a todo about moving it. This commit will break compilation on its own in a couple of places; subsequent commits will fix it up.
2022-03-25 20:44:12 +00:00
"tor-guardmgr",
arti-client: Create an HsClientConnector
2023-03-21 17:28:28 +00:00
"tor-hsclient",
Make a top-level API for connecting to onion services. Fortunately, it adds very little to the arti-client API surface.
2023-01-12 14:28:58 +00:00
"tor-hscrypto",
keymgr: Add key manager implementation stub.
2023-05-31 11:05:40 +01:00
"tor-keymgr",
Add "accel-*" features to arti-client and arti. These need to be optional: they improve performance by shifting to asm implementations, which may not be everybody's idea of good practice. These are not 'pure' features, since they select one implementation but disable another. Therefore they don't go in `full`. Closes #441.
2022-06-13 15:20:06 +01:00
"tor-llcrypto",
Update arti-client to new NetDirProvider API. This allows us to give better errors in the case where bootstrapping succeeds at first, but fails thereafter for long enough to make our directory expire.
2022-07-25 17:06:37 +01:00
"tor-netdir",
Change type of TorClientConfig::override_net_params Now we use NetParams. That implies making its constructor public, which I think it fine. This is related to #413 but is far from completing that ticket.
2022-03-16 18:25:06 +00:00
"tor-netdoc",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-persist",
"tor-proto",
tor-ptmgr: make configuration use builders, plumb into arti-client This brings the draft configuration mechanisms in tor-ptmgr in line with the config in other crates, using builders. It also plumbs the config type through into the main `arti-client` config, and adds some example lines to `arti-example-config.toml`.
2022-11-03 14:36:31 +00:00
"tor-ptmgr",
RPC: Start on plumbing TorClient into our RPC code Because of #837, we won't be able to work with _every_ TorClient<R>, so I'm only going to be using TorClient<PreferredRuntime> for now.
2023-04-20 19:17:16 +01:00
"tor-rpcbase",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-rtcompat",
"tracing",
Remove usage of tracing-test 0.1 It requires tracing-subscriber 0.2, which is a lower version than we want, and which causes trouble with our minimal-versions CI test. There is a pending issue to fix this; we can reinstate tracing-test once it is merged: https://github.com/dbrgn/tracing-test/pull/11
2021-11-11 15:58:25 +00:00
"tracing-subscriber",
arti-client: Parse .onion addresses and dispatch to client.rs Now, a Host has a separate variant for `.onion` which is always used, even when HS is disabled. Currently it ends in a todo!.
2023-03-08 17:02:18 +00:00
"void",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Move top-level configuration downwards from `arti` to `arti-config`. 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.
2021-11-17 19:16:55 +00:00
[[package]]
name = "arti-config"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.6.2"
Move top-level configuration downwards from `arti` to `arti-config`. 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.
2021-11-17 19:16:55 +00:00
arti-hyper: empty crate skeleton
2022-02-23 11:59:36 +00:00
[[package]]
name = "arti-hyper"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.9.2"
arti-hyper: empty crate skeleton
2022-02-23 11:59:36 +00:00
dependencies = [
arti-hyper: Move hyper example from arti-client Code motion and consequential dependency adjustments.
2022-02-23 12:02:10 +00:00
"anyhow",
arti-hyper: empty crate skeleton
2022-02-23 11:59:36 +00:00
"arti-client",
Replace manual Clone impl with educe in arti-hyper
2022-03-02 14:58:06 +00:00
"educe",
arti-hyper: empty crate skeleton
2022-02-23 11:59:36 +00:00
"hyper",
arti-hyper: Move hyper example from arti-client Code motion and consequential dependency adjustments.
2022-02-23 12:02:10 +00:00
"pin-project",
arti-hyper: Introduce new ConnectionError type We need this not to use anyhow because we don't want our libraries to expose anyhow, and this is about to go into the library.
2022-02-23 12:59:58 +00:00
"thiserror",
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
"tls-api",
"tls-api-native-tls",
Updated Cargo.lock
2023-01-06 17:35:32 +00:00
"tls-api-openssl",
arti-hyper: Move hyper example from arti-client Code motion and consequential dependency adjustments.
2022-02-23 12:02:10 +00:00
"tokio",
arti-hyper: impl HasKind for ConnectionError
2022-02-23 13:53:19 +00:00
"tor-error",
arti-hyper: Move hyper example from arti-client Code motion and consequential dependency adjustments.
2022-02-23 12:02:10 +00:00
"tor-rtcompat",
"tracing-subscriber",
arti-hyper: empty crate skeleton
2022-02-23 11:59:36 +00:00
]
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
[[package]]
name = "arti-rpcserver"
Bump minor versions on crates with breaking changes Done with: ``` cargo set-version --bump minor -p tor-hsclient cargo set-version --bump minor -p arti-rpcserver cargo set-version --bump minor -p tor-hscrypto cargo set-version --bump minor -p tor-cell ```
2023-06-30 13:38:16 +01:00
version = "0.2.0"
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
dependencies = [
"arti-client",
"asynchronous-codec",
rpc: Change the formatting of object IDs We want each ID to have a unique form every time it is given out, so that you can't use ID==ID to check whether Object==Object. (See discussions leading to #848.) We'd also like the form of object IDs to be a little annoying to analyze, to discourage people from writing programs that depends on their particular format. (We are reserving the right to change the format whenever we want.) We _don't_ want to use any cryptography here (yet), lest somebody think that this is an actual security mechanism. (This isn't for security; it's for encouraging developers to treat IDs as opaque.) With that in mind, we now lightly obfuscate our generational indices before returning them.
2023-05-15 20:21:49 +01:00
"base64ct",
rpc: Add asynchronous_codec wrapper for jsonlines.
2023-03-29 17:25:35 +01:00
"bytes",
rpc: Give RpcMgr a registry of connections. We're going to use this to implement arti#863, which requires that some RPC objects be globally nameable.
2023-05-25 15:09:22 +01:00
"derive_more",
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
"erased-serde",
"futures",
rpc: Add a cancellable future type. Ordinarily you can cancel a future just by dropping it, but we'll want the ability to cancel futures that we no longer own (because we gave them to a `FuturesUnordered`).
2023-03-29 16:45:44 +01:00
"futures-await-test",
rpc: Remove fake_generational_arena Now that generation-arena has merged [@diziet's patch] to clarify their license, we no longer need to disable it. [@diziet's patch]: https://github.com/fitzgen/generational-arena/pull/56
2023-05-23 18:55:23 +01:00
"generational-arena",
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
"pin-project",
rpc: Change the formatting of object IDs We want each ID to have a unique form every time it is given out, so that you can't use ID==ID to check whether Object==Object. (See discussions leading to #848.) We'd also like the form of object IDs to be a little annoying to analyze, to discourage people from writing programs that depends on their particular format. (We are reserving the right to change the format whenever we want.) We _don't_ want to use any cryptography here (yet), lest somebody think that this is an actual security mechanism. (This isn't for security; it's for encouraging developers to treat IDs as opaque.) With that in mind, we now lightly obfuscate our generational indices before returning them.
2023-05-15 20:21:49 +01:00
"rand 0.8.5",
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
"serde",
"serde_json",
rpc: Add a cancellable future type. Ordinarily you can cancel a future just by dropping it, but we'll want the ability to cancel futures that we no longer own (because we gave them to a `FuturesUnordered`).
2023-03-29 16:45:44 +01:00
"thiserror",
RPC: Implement a "global identifier" for non-session-bound IDs These identifiers are actually only "global" with respect to a given `RpcMgr`, but they should not be forgeable or reusable across RpcMgr objects. We're going to use them so that we have a kind of identifier for `TorClient`s that we can expose to SOCKS.
2023-05-25 19:40:26 +01:00
"tiny-keccak",
rpcserver: Use with_fn.
2023-04-18 20:55:08 +01:00
"tor-async-utils",
rpc: Change the formatting of object IDs We want each ID to have a unique form every time it is given out, so that you can't use ID==ID to check whether Object==Object. (See discussions leading to #848.) We'd also like the form of object IDs to be a little annoying to analyze, to discourage people from writing programs that depends on their particular format. (We are reserving the right to change the format whenever we want.) We _don't_ want to use any cryptography here (yet), lest somebody think that this is an actual security mechanism. (This isn't for security; it's for encouraging developers to treat IDs as opaque.) With that in mind, we now lightly obfuscate our generational indices before returning them.
2023-05-15 20:21:49 +01:00
"tor-basic-utils",
"tor-bytes",
rpc: Add an authentication step. Per our design, every connection starts out unauthenticated, and needs one authenticate command to become authenticated. Right now the only authentication type is "This is a unix named socket where everybody who can connect has permission."
2023-04-05 17:07:47 +01:00
"tor-error",
RPC: Implement a "global identifier" for non-session-bound IDs These identifiers are actually only "global" with respect to a given `RpcMgr`, but they should not be forgeable or reusable across RpcMgr objects. We're going to use them so that we have a kind of identifier for `TorClient`s that we can expose to SOCKS.
2023-05-25 19:40:26 +01:00
"tor-llcrypto",
Rename tor-rpccmd to tor-rpcbase.
2023-04-11 20:13:19 +01:00
"tor-rpcbase",
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
"tor-rtcompat",
RPC: add a temporary "listen" function. It requires tokio, it's unix-only, and makes some unfortunate shortcuts. Probably good enough for initial testing.
2023-04-05 13:14:27 +01:00
"tracing",
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
"typetag",
rpc: Give RpcMgr a registry of connections. We're going to use this to implement arti#863, which requires that some RPC objects be globally nameable.
2023-05-25 15:09:22 +01:00
"weak-table",
RPC: Implement a "global identifier" for non-session-bound IDs These identifiers are actually only "global" with respect to a given `RpcMgr`, but they should not be forgeable or reusable across RpcMgr objects. We're going to use them so that we have a kind of identifier for `TorClient`s that we can expose to SOCKS.
2023-05-25 19:40:26 +01:00
"zeroize",
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
]
arti-testing: Initial implementation This commit adds a new program to try to implement the ideas behind experimentation in arti#329. In particular, it tries to implement basic client "can I bootstrap and connect" functionality testing, with a lot of instrumentation, and support for breaking things. So far, the instrumentation is limited to counting TCP bytes and connections, and counting events. Still, this is enough to measure behavior on some of the incorrect-clock tests. NOTE: For now, you are _required_ to pass in an explicit configuration, in hopes that this will lead you to override your storage directories for doing specific experiments.
2022-03-02 15:03:19 +00:00
[[package]]
name = "arti-testing"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.8.6"
arti-testing: Initial implementation This commit adds a new program to try to implement the ideas behind experimentation in arti#329. In particular, it tries to implement basic client "can I bootstrap and connect" functionality testing, with a lot of instrumentation, and support for breaking things. So far, the instrumentation is limited to counting TCP bytes and connections, and counting events. Still, this is enough to measure behavior on some of the incorrect-clock tests. NOTE: For now, you are _required_ to pass in an explicit configuration, in hopes that this will lead you to override your storage directories for doing specific experiments.
2022-03-02 15:03:19 +00:00
dependencies = [
"anyhow",
Move ArtiConfig to new arti::cfg module Code motion and import fixups.
2022-03-21 10:23:22 +00:00
"arti",
arti-testing: Initial implementation This commit adds a new program to try to implement the ideas behind experimentation in arti#329. In particular, it tries to implement basic client "can I bootstrap and connect" functionality testing, with a lot of instrumentation, and support for breaking things. So far, the instrumentation is limited to counting TCP bytes and connections, and counting events. Still, this is enough to measure behavior on some of the incorrect-clock tests. NOTE: For now, you are _required_ to pass in an explicit configuration, in hopes that this will lead you to override your storage directories for doing specific experiments.
2022-03-02 15:03:19 +00:00
"arti-client",
"async-trait",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
arti-testing: Initial implementation This commit adds a new program to try to implement the ideas behind experimentation in arti#329. In particular, it tries to implement basic client "can I bootstrap and connect" functionality testing, with a lot of instrumentation, and support for breaking things. So far, the instrumentation is limited to counting TCP bytes and connections, and counting events. Still, this is enough to measure behavior on some of the incorrect-clock tests. NOTE: For now, you are _required_ to pass in an explicit configuration, in hopes that this will lead you to override your storage directories for doing specific experiments.
2022-03-02 15:03:19 +00:00
"clap",
"config",
"futures",
"pin-project",
arti-testing: Initial support for broken TCP. This commit adds support for a BrokenTcp provider that can make connection attempts fail or time out. It doesn't yet have a way to turn on the failure.
2022-03-04 22:43:17 +00:00
"rand 0.8.5",
arti-testing: Initial implementation This commit adds a new program to try to implement the ideas behind experimentation in arti#329. In particular, it tries to implement basic client "can I bootstrap and connect" functionality testing, with a lot of instrumentation, and support for breaking things. So far, the instrumentation is limited to counting TCP bytes and connections, and counting events. Still, this is enough to measure behavior on some of the incorrect-clock tests. NOTE: For now, you are _required_ to pass in an explicit configuration, in hopes that this will lead you to override your storage directories for doing specific experiments.
2022-03-02 15:03:19 +00:00
"serde",
"tokio",
rng ranges: Use gen_range_infallible() for Duration::ZERO..=T
2023-07-07 14:19:55 +01:00
"tor-basic-utils",
Directory filtering in arti-testing. This feature allows us to detect different failing cases for arti#329 that would otherwise be hard to induce. It works by filtering consensus directory objects and/or microdescriptor objects before introducing them to the directory manager. Closes #397.
2022-03-30 13:48:35 +01:00
"tor-checkable",
arti-config abolition: Change references to use tor_config Generally, change the paths that mention the crate name to go via a module-level "use". This involves adding tor-config as a direct dependency for a few crates.
2022-05-13 11:36:28 +01:00
"tor-config",
Directory filtering in arti-testing. This feature allows us to detect different failing cases for arti#329 that would otherwise be hard to induce. It works by filtering consensus directory objects and/or microdescriptor objects before introducing them to the directory manager. Closes #397.
2022-03-30 13:48:35 +01:00
"tor-dirmgr",
"tor-error",
"tor-netdoc",
arti-testing: Initial implementation This commit adds a new program to try to implement the ideas behind experimentation in arti#329. In particular, it tries to implement basic client "can I bootstrap and connect" functionality testing, with a lot of instrumentation, and support for breaking things. So far, the instrumentation is limited to counting TCP bytes and connections, and counting events. Still, this is enough to measure behavior on some of the incorrect-clock tests. NOTE: For now, you are _required_ to pass in an explicit configuration, in hopes that this will lead you to override your storage directories for doing specific experiments.
2022-03-02 15:03:19 +00:00
"tor-rtcompat",
"tracing",
"tracing-appender",
"tracing-subscriber",
]
netdoc: Use derive amplify::Getters for HsDesc accessors. Closes #909.
2023-06-20 19:00:41 +01:00
[[package]]
name = "ascii"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d92bec98840b8f03a5ff5413de5293bfcd8bf96467cf5452609f939ec6f5de16"
RPC: Initial implementation of a multiple-argument dispatch This code uses some kludges (discussed with Ian previously and hopefully well documented here) to get a type-identifier for each type in a const context. It then defines a macro to declare a type-erased versions of a concrete implementation functions, and register those implementations to be called later. We will probably want to tweak a bunch of this code as we move ahead.
2023-04-03 15:23:55 +01:00
[[package]]
name = "assert-impl"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c3464313de0c867016e3e69d7e1e9ae3499bcc4c18e12283d381359ed38b5b9e"
Initial cut at a typed event framework for arti (arti#230). This implements a basic typed event broadcast mechanism, as described in arti#230: consumers of the new `tor-events` crate can emit `TorEvent` events, which others can consume via the `TorEventReceiver`. Under the hood, the crate uses the `async-broadcast` (https://github.com/smol-rs/async-broadcast) crate, and a `futures::mpsc::UnboundedSender` for the event emitters; these are glued together in the `EventReactor`, which must be run in a background thread for things to work. (This is done so event sending is always cheap and non-blocking, since `async-broadcast` senders don't have this functionality.) Additionally, the `TorEventKind` type is used to implement selective event reception / emission: receivers can subscribe to certain event types (and in fact start out receiving nothing), which filters the set of events they receive. Having no subscribers for a given event type means it won't even be emitted in the first place, making things more efficient.
2021-11-16 15:21:47 +00:00
[[package]]
name = "async-broadcast"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
version = "0.5.1"
Initial cut at a typed event framework for arti (arti#230). This implements a basic typed event broadcast mechanism, as described in arti#230: consumers of the new `tor-events` crate can emit `TorEvent` events, which others can consume via the `TorEventReceiver`. Under the hood, the crate uses the `async-broadcast` (https://github.com/smol-rs/async-broadcast) crate, and a `futures::mpsc::UnboundedSender` for the event emitters; these are glued together in the `EventReactor`, which must be run in a background thread for things to work. (This is done so event sending is always cheap and non-blocking, since `async-broadcast` senders don't have this functionality.) Additionally, the `TorEventKind` type is used to implement selective event reception / emission: receivers can subscribe to certain event types (and in fact start out receiving nothing), which filters the set of events they receive. Having no subscribers for a given event type means it won't even be emitted in the first place, making things more efficient.
2021-11-16 15:21:47 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
checksum = "7c48ccdbf6ca6b121e0f586cbc0e73ae440e56c67c30fa0873b4e110d9c26d2b"
Initial cut at a typed event framework for arti (arti#230). This implements a basic typed event broadcast mechanism, as described in arti#230: consumers of the new `tor-events` crate can emit `TorEvent` events, which others can consume via the `TorEventReceiver`. Under the hood, the crate uses the `async-broadcast` (https://github.com/smol-rs/async-broadcast) crate, and a `futures::mpsc::UnboundedSender` for the event emitters; these are glued together in the `EventReactor`, which must be run in a background thread for things to work. (This is done so event sending is always cheap and non-blocking, since `async-broadcast` senders don't have this functionality.) Additionally, the `TorEventKind` type is used to implement selective event reception / emission: receivers can subscribe to certain event types (and in fact start out receiving nothing), which filters the set of events they receive. Having no subscribers for a given event type means it won't even be emitted in the first place, making things more efficient.
2021-11-16 15:21:47 +00:00
dependencies = [
"event-listener",
"futures-core",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "async-channel"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "1.8.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "cf46fee83e5ccffc220104713af3292ff9bc7c64c7de289f66dae8e38d826833"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
"concurrent-queue",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"event-listener",
"futures-core",
]
[[package]]
name = "async-compression"
Upgrade async-compression dependency to 0.4.0.
2023-05-22 12:52:18 +01:00
version = "0.4.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade async-compression dependency to 0.4.0.
2023-05-22 12:52:18 +01:00
checksum = "5b0122885821398cc923ece939e24d1056a2384ee719432397fa9db87230ff11"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"flate2",
"futures-core",
"futures-io",
"memchr",
"pin-project-lite",
"xz2",
"zstd",
"zstd-safe",
]
[[package]]
name = "async-ctrlc"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "907279f6e91a51c8ec7cac24711e8308f21da7c10c7700ca2f7e125694ed2df1"
dependencies = [
"ctrlc",
]
[[package]]
name = "async-executor"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "1.5.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "6fa3dc5f2a8564f07759c008b9109dc0d39de92a88d5588b8a5036d286383afb"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
"async-lock",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"async-task",
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
"concurrent-queue",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"fastrand",
"futures-lite",
"slab",
]
[[package]]
name = "async-global-executor"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
version = "2.3.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
checksum = "f1b6f5d7df27bd294849f8eec66ecfc63d11814df7a4f5d74168a2394467b776"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"async-channel",
"async-executor",
"async-io",
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
"async-lock",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"blocking",
"futures-lite",
"once_cell",
]
[[package]]
name = "async-io"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "1.13.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "0fc5b45d93ef0529756f812ca52e44c221b35341892d3dcc34132ac02f3dd2af"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
"async-lock",
Run cargo update in preparation for release.
2022-08-30 16:22:51 +01:00
"autocfg",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
"concurrent-queue",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"futures-lite",
"log",
"parking",
"polling",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"rustix",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"slab",
"socket2",
"waker-fn",
]
[[package]]
name = "async-lock"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "2.7.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "fa24f727524730b077666307f2734b4a1a1c57acb79193127dcc8914d5242dd7"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"event-listener",
]
[[package]]
name = "async-native-tls"
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
version = "0.5.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
checksum = "9343dc5acf07e79ff82d0c37899f079db3534d99f189a1837c8e549c99405bec"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Upgrade to async-native-tls 0.4.0
2021-11-12 13:36:41 +00:00
"futures-util",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"native-tls",
"thiserror",
"url",
]
[[package]]
name = "async-process"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "1.7.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "7a9d28b1d97e08915212e2e45310d47854eafa69600756fc735fb788f75199c9"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"async-io",
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
"async-lock",
Run cargo update in preparation for release.
2022-08-30 16:22:51 +01:00
"autocfg",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"blocking",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"event-listener",
"futures-lite",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"rustix",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"signal-hook",
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
"windows-sys 0.48.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
[[package]]
name = "async-rustls"
update rustls to 0.21
2023-05-08 17:01:00 +01:00
version = "0.4.0"
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update rustls to 0.21
2023-05-08 17:01:00 +01:00
checksum = "29479d362e242e320fa8f5c831940a5b83c1679af014068196cd20d4bf497b6b"
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
dependencies = [
upgrade rustls to 0.20, ignoring all deprecation warnings
2022-10-31 19:06:13 +00:00
"futures-io",
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
"rustls",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "async-std"
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
version = "1.12.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
checksum = "62565bb4402e926b29953c785397c6dc0391b7b446e45008b0049eb43cec6f5d"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"async-channel",
"async-global-executor",
"async-io",
"async-lock",
"async-process",
"crossbeam-utils",
"futures-channel",
"futures-core",
"futures-io",
"futures-lite",
"gloo-timers",
"kv-log-macro",
"log",
"memchr",
"once_cell",
"pin-project-lite",
"pin-utils",
"slab",
"wasm-bindgen-futures",
]
[[package]]
name = "async-task"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "4.4.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "ecc7ab41815b3c653ccd2978ec3255c81349336702dfdf62ee6f7069b12a3aae"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "async-trait"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.1.68"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "b9ccdd8f2a161be9bd5c023df56f1b2a0bd1d83872ae53b71a84a12c9bf6e842"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "async_executors"
Bump async_executors to 0.6
2022-04-25 20:47:14 +01:00
version = "0.6.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump async_executors to 0.6
2022-04-25 20:47:14 +01:00
checksum = "c0b2463773401e1f684136f9cdb956cf611f22172472cf3f049e72123f59e359"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"async-std",
"blanket",
"futures-core",
"futures-task",
"futures-util",
"pin-project",
Run "cargo update" to get latest versions. Also fix a couple of warnings introduced by now-unneeded imports with new ed25519 crate. This is part of the process for releasing our next version.
2021-11-29 19:45:50 +00:00
"rustc_version",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tokio",
]
[[package]]
name = "asynchronous-codec"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
version = "0.6.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
checksum = "06a0daa378f5fd10634e44b0a29b2a87b890657658e072a30d6f26e57ddee182"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"bytes",
"futures-sink",
"futures-util",
"memchr",
"pin-project-lite",
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
"serde",
"serde_json",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "atomic"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.5.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "c59bdb34bc650a32731b31bd8f0829cc15d24a708ee31559e0bb34f2bc320cba"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "atomic-waker"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "1.1.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "1181e1e0d1fce796a03db1ae795d67167da795f9cf4a39c37589e85ef57f26d3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
[[package]]
name = "atty"
version = "0.2.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
dependencies = [
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
"hermit-abi 0.1.19",
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
"libc",
update to v5.0.0
2022-08-12 19:50:08 +01:00
"winapi",
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "autocfg"
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
version = "1.1.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
checksum = "d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
[[package]]
name = "backtrace"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "0.3.67"
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "233d376d6d185f2a3093e58f283f60f880315b6c60075b01f36b3b85154564ca"
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
dependencies = [
"addr2line",
"cc",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
"libc",
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
"miniz_oxide 0.6.2",
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
"object",
"rustc-demangle",
]
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "base16ct"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "349a06037c7bf932dd7e7d1f653678b2038b9ad46a74102f1fc7bd7872678cce"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "base64"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
version = "0.13.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
checksum = "9e1b586273c5702936fe7b7d6896644d8be71e6314cfe09d3167c95f712589e8"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
Upgrade serde_with dependency to 3.0.0
2023-05-22 12:49:58 +01:00
[[package]]
name = "base64"
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
version = "0.21.2"
Upgrade serde_with dependency to 3.0.0
2023-05-22 12:49:58 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
checksum = "604178f6c5c21f02dc555784810edfb88d34ac2c73b2eae109655649ee73ce3d"
Upgrade serde_with dependency to 3.0.0
2023-05-22 12:49:58 +01:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "base64ct"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
version = "1.6.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
checksum = "8c3c1a368f70d6cf7302d78f8f7093da241fb8e8807c05cc9e51a125895a6d5b"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "bitflags"
version = "1.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
Upgrade to bitflags 2.0 This version of bitflags now requires us to explicitly list the traits that we want to derive for our bit-flags structs.
2023-03-13 12:47:14 +00:00
[[package]]
name = "bitflags"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "2.3.3"
Upgrade to bitflags 2.0 This version of bitflags now requires us to explicitly list the traits that we want to derive for our bit-flags structs.
2023-03-13 12:47:14 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "630be753d4e58660abd17930c71b647fe46c27ea6b63cc59e1e3851406972e42"
Upgrade to bitflags 2.0 This version of bitflags now requires us to explicitly list the traits that we want to derive for our bit-flags structs.
2023-03-13 12:47:14 +00:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "blanket"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7b04ce3d2372d05d1ef4ea3fdf427da6ae3c17ca06d688a107b5344836276bc3"
dependencies = [
"proc-macro2",
"quote",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "block-buffer"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4152116fd6e9dadb291ae18fc1ec3575ed6d84c29642d97890f4b4a3417297e4"
dependencies = [
"generic-array",
]
[[package]]
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
name = "block-buffer"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.10.4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "3078c7629b62d3f0439517fa394996acacc5cbc91c5a20d8c658e77abd503a71"
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
dependencies = [
"generic-array",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "blocking"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "1.3.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "77231a1c8f801696fc0123ec6150ce92cffb8e164a02afb9c8ddee0e9b65ad65"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"async-channel",
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
"async-lock",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"async-task",
"atomic-waker",
"fastrand",
"futures-lite",
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
"log",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "bounded-vec-deque"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2225b558afc76c596898f5f1b3fc35cfce0eb1b13635cbd7d1b2a7177dc10ccd"
[[package]]
name = "bumpalo"
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
version = "3.13.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
checksum = "a3e2c3daef883ecc1b5d58c15adae93470a91d425f3532ba1695849656af3fc1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
linkspec: Add an "all_overlapping" accessor to ByRelayIds. Also, add a few tests for this and the other accessors. We'll need this accessor to find whether we have any channels to _any_ of the identities that we're trying to connect to.
2022-10-14 17:31:16 +01:00
[[package]]
name = "by_address"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
version = "1.1.0"
linkspec: Add an "all_overlapping" accessor to ByRelayIds. Also, add a few tests for this and the other accessors. We'll need this accessor to find whether we have any channels to _any_ of the identities that we're trying to connect to.
2022-10-14 17:31:16 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
checksum = "bf8dba2868114ed769a1f2590fc9ae5eb331175b44313b6c9b922f8f7ca813d0"
linkspec: Add an "all_overlapping" accessor to ByRelayIds. Also, add a few tests for this and the other accessors. We'll need this accessor to find whether we have any channels to _any_ of the identities that we're trying to connect to.
2022-10-14 17:31:16 +01:00
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
[[package]]
name = "bytemuck"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "1.13.1"
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "17febce684fd15d89027105661fec94afb475cb995fbc59d2865198446ba2eea"
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "byteorder"
version = "1.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "14c189c53d098945499cdfa7ecc63567cf3886b3332b312a5b4585d8d3a6a610"
[[package]]
name = "bytes"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "1.4.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "89b2fd2a0dcf38d7971e2194b6b6eebab45ae01067456a7fd93d5547a61b70be"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "caret"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.4.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "cc"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "1.0.79"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "50d30906286121d95be3d479533b458f87493b30a4b5f79a607db8f5d11aa91f"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"jobserver",
]
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
[[package]]
name = "chrono"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.4.26"
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "ec837a71355b28f6556dbd569b37b3f363091c0bd4b2e735674521b4c5fd9bc5"
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
dependencies = [
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
"android-tzdata",
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
"iana-time-zone",
"num-traits",
"serde",
"winapi",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "cipher"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.4.4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "773f3b9af64447d2ce9850330c473515014aa235e6a783b02db81ff39e4a3dad"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Upgrade to AES 0.8 Now that we require Rust 1.56, we can upgrade to AES 0.8. This forces us to have some slight API changes. We require cipher 0.4.1, not cipher 0.4.0, since 0.4.0 has compatibility issues with Rust 1.56.
2022-04-25 20:39:26 +01:00
"crypto-common",
"inout",
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
"zeroize",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
[[package]]
name = "clap"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
version = "3.2.25"
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
checksum = "4ea181bf566f71cb9a5d17a59e1871af638180a18fb0035c92ae62b705207123"
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
dependencies = [
"atty",
Upgrade to bitflags 2.0 This version of bitflags now requires us to explicitly list the traits that we want to derive for our bit-flags structs.
2023-03-13 12:47:14 +00:00
"bitflags 1.3.2",
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
"clap_lex",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"indexmap 1.9.3",
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
"strsim",
"termcolor",
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
"textwrap",
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
]
[[package]]
name = "clap_lex"
version = "0.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2850f2f5a82cbf437dd5af4d49848fbdfc27c157c3d010345776f952765261c5"
dependencies = [
"os_str_bytes",
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
]
Use coarsetime to build an incoming traffic timestamp. We need this for the circuit timeout estimator (#57). It needs to know "how recently have we got some incoming traffic", so that it can tell whether a circuit has truly timed out, or whether the entire network is down. I'm implementing this with coarsetime, since we need to update these in response to every single incoming cell, and we need the timestamp operation to be _fast_. (This reinstates an earlier commit, f30b2280, which I reverted because we didn't need it at the time.) Closes #179.
2021-07-13 15:35:46 +01:00
[[package]]
name = "coarsetime"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
version = "0.1.23"
Use coarsetime to build an incoming traffic timestamp. We need this for the circuit timeout estimator (#57). It needs to know "how recently have we got some incoming traffic", so that it can tell whether a circuit has truly timed out, or whether the entire network is down. I'm implementing this with coarsetime, since we need to update these in response to every single incoming cell, and we need the timestamp operation to be _fast_. (This reinstates an earlier commit, f30b2280, which I reverted because we didn't need it at the time.) Closes #179.
2021-07-13 15:35:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
checksum = "a90d114103adbc625300f346d4d09dfb4ab1c4a8df6868435dd903392ecf4354"
Use coarsetime to build an incoming traffic timestamp. We need this for the circuit timeout estimator (#57). It needs to know "how recently have we got some incoming traffic", so that it can tell whether a circuit has truly timed out, or whether the entire network is down. I'm implementing this with coarsetime, since we need to update these in response to every single incoming cell, and we need the timestamp operation to be _fast_. (This reinstates an earlier commit, f30b2280, which I reverted because we didn't need it at the time.) Closes #179.
2021-07-13 15:35:46 +01:00
dependencies = [
"libc",
"once_cell",
Run "cargo update" in preparation for monday's release.
2022-01-28 13:38:54 +00:00
"wasi 0.11.0+wasi-snapshot-preview1",
Use coarsetime to build an incoming traffic timestamp. We need this for the circuit timeout estimator (#57). It needs to know "how recently have we got some incoming traffic", so that it can tell whether a circuit has truly timed out, or whether the entire network is down. I'm implementing this with coarsetime, since we need to update these in response to every single incoming cell, and we need the timestamp operation to be _fast_. (This reinstates an earlier commit, f30b2280, which I reverted because we didn't need it at the time.) Closes #179.
2021-07-13 15:35:46 +01:00
"wasm-bindgen",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "concurrent-queue"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "2.2.0"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "62ec6771ecfa0762d24683ee5a32ad78487a3d3afdc0fb8cae19d2c5deb50b7c"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
dependencies = [
"crossbeam-utils",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "config"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "0.13.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "d379af7f68bfc21714c6c7dea883544201741d2ce8274bb12fa54f89507f52a7"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Upgrade to newer version of config crate.
2022-02-25 14:17:37 +00:00
"async-trait",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"lazy_static",
"nom",
Upgrade to newer version of config crate.
2022-02-25 14:17:37 +00:00
"pathdiff",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"serde",
Upgrade toml to version 0.6. This required rewriting some of our error handling code in command-line processing, since the toml crate now displays and reports errors differently. (Admittedly, this code still is kind of ugly, but at least it is nicely hidden.)
2023-01-25 21:29:53 +00:00
"toml 0.5.11",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "const-oid"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
version = "0.9.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
checksum = "520fbf3c07483f94e3e3ca9d0cfd913d7718ef2483d2cfd91c0d9e91474ab913"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "convert_case"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6245d59a3e82a7fc217c5828a6692dbc6dfb63a0c8c90495621f7b9d79704a0e"
[[package]]
name = "core-foundation"
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
version = "0.9.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
checksum = "194a7a9e6de53fa55116934067c844d9d749312f75c6f6d0980e8c252f8c2146"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"core-foundation-sys",
"libc",
]
[[package]]
name = "core-foundation-sys"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "0.8.4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "e496a50fda8aacccc86d7529e2c1e0892dbd0f898a6b5645b5561b89c3210efa"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "cpufeatures"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.2.8"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "03e69e28e9f7f77debdedbaafa2866e1de9ba56df55a8bd7cfc724c25a09987c"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"libc",
]
[[package]]
name = "crc32fast"
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
version = "1.3.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
checksum = "b540bd8bc810d3885c6ea91e2018302f68baba2129ab3e88f32389ee9370880d"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Tracing configuration for logfiles, per-target filters Previously we could only configure one global tracing filter that applied to stdout and journald. There was no support for log files, either. This patch fixes both issues, by substantially revising the configuration format: There are now separate filters for each log file, for journald, and for the console log. Because we want to allow multiple logfiles, they have to go into an array in the configuration. The configuration logic has grown a bit complicated in its types, since the tracing_subscriber crate would prefer to have the complete structure of tracing Layers known statically. That's fine when you know how many you have, and which kinds there will be, but for the runtime-configuration case we need to mess around with `Box<dyn Layer ...>`. I also had to switch from tracing_subscriber's EnvFilter to its Targets filter. It seems "EnvFilter" can only be applied as a Layer in itself, and won't work as a Filter on an individual Layer. Closes #166. Closes #170.
2022-01-07 15:52:43 +00:00
[[package]]
name = "crossbeam-channel"
Update to new version of crossbeam-channel. The previous one is yanked, which is making our cargo-audit script fail.
2023-04-10 12:35:17 +01:00
version = "0.5.8"
Tracing configuration for logfiles, per-target filters Previously we could only configure one global tracing filter that applied to stdout and journald. There was no support for log files, either. This patch fixes both issues, by substantially revising the configuration format: There are now separate filters for each log file, for journald, and for the console log. Because we want to allow multiple logfiles, they have to go into an array in the configuration. The configuration logic has grown a bit complicated in its types, since the tracing_subscriber crate would prefer to have the complete structure of tracing Layers known statically. That's fine when you know how many you have, and which kinds there will be, but for the runtime-configuration case we need to mess around with `Box<dyn Layer ...>`. I also had to switch from tracing_subscriber's EnvFilter to its Targets filter. It seems "EnvFilter" can only be applied as a Layer in itself, and won't work as a Filter on an individual Layer. Closes #166. Closes #170.
2022-01-07 15:52:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to new version of crossbeam-channel. The previous one is yanked, which is making our cargo-audit script fail.
2023-04-10 12:35:17 +01:00
checksum = "a33c2bf77f2df06183c3aa30d1e96c0695a313d4f9c453cc3762a6db39f99200"
Tracing configuration for logfiles, per-target filters Previously we could only configure one global tracing filter that applied to stdout and journald. There was no support for log files, either. This patch fixes both issues, by substantially revising the configuration format: There are now separate filters for each log file, for journald, and for the console log. Because we want to allow multiple logfiles, they have to go into an array in the configuration. The configuration logic has grown a bit complicated in its types, since the tracing_subscriber crate would prefer to have the complete structure of tracing Layers known statically. That's fine when you know how many you have, and which kinds there will be, but for the runtime-configuration case we need to mess around with `Box<dyn Layer ...>`. I also had to switch from tracing_subscriber's EnvFilter to its Targets filter. It seems "EnvFilter" can only be applied as a Layer in itself, and won't work as a Filter on an individual Layer. Closes #166. Closes #170.
2022-01-07 15:52:43 +00:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
Tracing configuration for logfiles, per-target filters Previously we could only configure one global tracing filter that applied to stdout and journald. There was no support for log files, either. This patch fixes both issues, by substantially revising the configuration format: There are now separate filters for each log file, for journald, and for the console log. Because we want to allow multiple logfiles, they have to go into an array in the configuration. The configuration logic has grown a bit complicated in its types, since the tracing_subscriber crate would prefer to have the complete structure of tracing Layers known statically. That's fine when you know how many you have, and which kinds there will be, but for the runtime-configuration case we need to mess around with `Box<dyn Layer ...>`. I also had to switch from tracing_subscriber's EnvFilter to its Targets filter. It seems "EnvFilter" can only be applied as a Layer in itself, and won't work as a Filter on an individual Layer. Closes #166. Closes #170.
2022-01-07 15:52:43 +00:00
"crossbeam-utils",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "crossbeam-queue"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
version = "0.3.8"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
checksum = "d1cfb3ea8a53f37c40dea2c7bedcbd88bdfae54f5e2175d6ecaff1c988353add"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"crossbeam-utils",
]
[[package]]
name = "crossbeam-utils"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.8.16"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "5a22b2d63d4d1dc0b7f1b6b2747dd0088008a9be28b6ddf0b1e7d335e3037294"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
RPC: Implement a "global identifier" for non-session-bound IDs These identifiers are actually only "global" with respect to a given `RpcMgr`, but they should not be forgeable or reusable across RpcMgr objects. We're going to use them so that we have a kind of identifier for `TorClient`s that we can expose to SOCKS.
2023-05-25 19:40:26 +01:00
[[package]]
name = "crunchy"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a81dae078cea95a014a339291cec439d2f232ebe854a9d672b796c6afafa9b7"
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "crypto-bigint"
version = "0.4.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ef2b4b23cddf68b89b8f8069890e8c270d54e2d5fe1b143820234805e4cb17ef"
dependencies = [
"generic-array",
"rand_core 0.6.4",
"subtle",
"zeroize",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
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
name = "crypto-common"
Run "cargo update" in preparation for next week's releases.
2022-07-20 13:37:13 +01:00
version = "0.1.6"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for next week's releases.
2022-07-20 13:37:13 +01:00
checksum = "1bfb12502f3fc46cca1bb51ac28df9d618d813cdc3d2f25b9fe775a34af26bb3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"generic-array",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"typenum",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "ctr"
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
version = "0.9.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
checksum = "0369ee1ad671834580515889b80f2ea915f23b8be8d0daa4bbaf2ac5c7590835"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"cipher",
]
[[package]]
name = "ctrlc"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "3.4.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "2a011bbe2c35ce9c1f143b7af6f94f29a167beb4cd1d29e6740ce836f723120e"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"nix",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"windows-sys 0.48.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "curve25519-dalek"
Update `rsa` dependency (and use `x25519-dalek` prerelease) - arti#448 and arti!607 highlight an issue with upgrading `rsa`: namely, the `x25519-dalek` version previously used has a hard dependency on `zeroize` 1.3, which creates a dependency conflict. - However, `x25519-dalek` version `2.0.0-pre.1` relaxes this dependency. Reviewing the changelogs, it doesn't look like that version is substantially different from the current one at all, so it should be safe to use despite the "prerelease" tag. - The new `x25519-dalek` version also bumps `rand_core`, which means we don't have to use the RNG compat wrapper in `tor-llcrypto` as much. closes arti#448
2022-07-05 11:57:10 +01:00
version = "3.2.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `rsa` dependency (and use `x25519-dalek` prerelease) - arti#448 and arti!607 highlight an issue with upgrading `rsa`: namely, the `x25519-dalek` version previously used has a hard dependency on `zeroize` 1.3, which creates a dependency conflict. - However, `x25519-dalek` version `2.0.0-pre.1` relaxes this dependency. Reviewing the changelogs, it doesn't look like that version is substantially different from the current one at all, so it should be safe to use despite the "prerelease" tag. - The new `x25519-dalek` version also bumps `rand_core`, which means we don't have to use the RNG compat wrapper in `tor-llcrypto` as much. closes arti#448
2022-07-05 11:57:10 +01:00
checksum = "0b9fdf9972b2bd6af2d913799d9ebc165ea4d2e65878e329d9c6b372c4491b61"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"byteorder",
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.9.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"rand_core 0.5.1",
"subtle",
"zeroize",
]
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
[[package]]
name = "darling"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.14.4"
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "7b750cb3417fd1b327431a470f388520309479ab0bf5e323505daf0290cd3850"
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
dependencies = [
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
"darling_core 0.14.4",
"darling_macro 0.14.4",
]
[[package]]
name = "darling"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.20.1"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "0558d22a7b463ed0241e993f76f09f30b126687447751a8638587b864e4b3944"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
dependencies = [
Run "cargo update".
2023-05-22 12:47:20 +01:00
"darling_core 0.20.1",
"darling_macro 0.20.1",
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "darling_core"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.14.4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "109c1ca6e6b7f82cc233a97004ea8ed7ca123a9af07a8230878fcfda9b158bf0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"fnv",
"ident_case",
"proc-macro2",
"quote",
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
"strsim",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
[[package]]
name = "darling_core"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.20.1"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "ab8bfa2e259f8ee1ce5e97824a3c55ec4404a0d772ca7fa96bf19f0752a046eb"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
dependencies = [
"fnv",
"ident_case",
"proc-macro2",
"quote",
"strsim",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "darling_macro"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.14.4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "a4aab4dbc9f7611d8b55048a3a16d2d010c2c8334e46304b40ac1cc14bf3b48e"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
"darling_core 0.14.4",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"quote",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
[[package]]
name = "darling_macro"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.20.1"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "29a358ff9f12ec09c3e61fef9b5a9902623a695a46a917b07f269bff1445611a"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
dependencies = [
Run "cargo update".
2023-05-22 12:47:20 +01:00
"darling_core 0.20.1",
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
]
Upgrade serial_test in preparation for release.
2022-08-30 16:19:34 +01:00
[[package]]
name = "dashmap"
Run cargo update again, in preparation for release
2022-08-31 16:09:26 +01:00
version = "5.4.0"
Upgrade serial_test in preparation for release.
2022-08-30 16:19:34 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update again, in preparation for release
2022-08-31 16:09:26 +01:00
checksum = "907076dfda823b0b36d2a1bb5f90c96660a5bbcd7729e10727f07858f22c4edc"
Upgrade serial_test in preparation for release.
2022-08-30 16:19:34 +01:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"hashbrown 0.12.3",
Upgrade serial_test in preparation for release.
2022-08-30 16:19:34 +01:00
"lock_api",
Run cargo update again, in preparation for release
2022-08-31 16:09:26 +01:00
"once_cell",
Upgrade serial_test in preparation for release.
2022-08-30 16:19:34 +01:00
"parking_lot_core",
]
actually add DNS support
2022-03-06 19:44:50 +00:00
[[package]]
name = "data-encoding"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "2.4.0"
actually add DNS support
2022-03-06 19:44:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "c2e66c9d817f1720209181c316d28635c050fa304f9c79e47a520882661b7308"
actually add DNS support
2022-03-06 19:44:50 +00:00
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "der"
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f1a467a65c5e759bce6e65eaf91cc29f466cdc57cb65777bd646872a8a1fd4de"
dependencies = [
"const-oid",
"pem-rfc7468 0.6.0",
"zeroize",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "der"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.7.6"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "56acb310e15652100da43d130af8d97b509e95af61aab1c5a7939ef24337ee17"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"const-oid",
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
"pem-rfc7468 0.7.0",
Upgrade rsa to 0.7. Closes #613.
2022-10-28 18:38:42 +01:00
"zeroize",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
tor-rtmock: Use derive-adhoc for composite runtimes
2023-07-06 15:46:35 +01:00
[[package]]
name = "derive-adhoc"
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3bf4f1be2a84b4ba6f6443854fc9c3b8942ee3ffadadc7106fa777659a946cd4"
dependencies = [
"derive-adhoc-macros",
"heck",
]
[[package]]
name = "derive-adhoc-macros"
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4a7134a81d247901c0d03ef80194867644796cd8f858e82bf1b433dfc1c35485"
dependencies = [
"heck",
"itertools 0.10.5",
"proc-macro-crate",
"proc-macro2",
"quote",
"sha3",
"strum",
"syn 1.0.109",
"void",
]
Fuzzer code for socks client implementation.
2022-09-27 22:16:14 +01:00
[[package]]
name = "derive_arbitrary"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "1.3.1"
Fuzzer code for socks client implementation.
2022-09-27 22:16:14 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "53e0efad4403bfc52dc201159c4b842a246a14b98c64b55dfd0f2d89729dfeb8"
Fuzzer code for socks client implementation.
2022-09-27 22:16:14 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
Fuzzer code for socks client implementation.
2022-09-27 22:16:14 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
name = "derive_builder_core_fork_arti"
Use git source for derive_builder for now, for sub_builder feature This commitid is the current head of my MR branch https://github.com/colin-kiegel/rust-derive-builder/pull/253 https://github.com/ijackson/rust-derive-builder/tree/field-builder Using the commitid prevents surprises if that branch is updated. We will require this newer version of derive_builder. The version will need to be bumped again later, assuming the upstream MR is merged and upstream do a release containing the needed changes. We will need the new version of not only `derive_builder_core` (the main macro implementation) but also`derive_builder` for a new error type.
2022-04-21 12:03:36 +01:00
version = "0.11.2"
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "24c1b715c79be6328caa9a5e1a387a196ea503740f0722ec3dd8f67a9e72314d"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
"darling 0.14.4",
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
"proc-macro2",
"quote",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
name = "derive_builder_fork_arti"
Use git source for derive_builder for now, for sub_builder feature This commitid is the current head of my MR branch https://github.com/colin-kiegel/rust-derive-builder/pull/253 https://github.com/ijackson/rust-derive-builder/tree/field-builder Using the commitid prevents surprises if that branch is updated. We will require this newer version of derive_builder. The version will need to be bumped again later, assuming the upstream MR is merged and upstream do a release containing the needed changes. We will need the new version of not only `derive_builder_core` (the main macro implementation) but also`derive_builder` for a new error type.
2022-04-21 12:03:36 +01:00
version = "0.11.2"
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c3eae24d595f4d0ecc90a9a5a6d11c2bd8dafe2375ec4a1ec63250e5ade7d228"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
"derive_builder_macro_fork_arti",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
name = "derive_builder_macro_fork_arti"
Use git source for derive_builder for now, for sub_builder feature This commitid is the current head of my MR branch https://github.com/colin-kiegel/rust-derive-builder/pull/253 https://github.com/ijackson/rust-derive-builder/tree/field-builder Using the commitid prevents surprises if that branch is updated. We will require this newer version of derive_builder. The version will need to be bumped again later, assuming the upstream MR is merged and upstream do a release containing the needed changes. We will need the new version of not only `derive_builder_core` (the main macro implementation) but also`derive_builder` for a new error type.
2022-04-21 12:03:36 +01:00
version = "0.11.2"
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "69887769a2489cd946bf782eb2b1bb2cb7bc88551440c94a765d4f040c08ebf3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
"derive_builder_core_fork_arti",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "derive_more"
Run "cargo update" to get latest versions. Also fix a couple of warnings introduced by now-unneeded imports with new ed25519 crate. This is part of the process for releasing our next version.
2021-11-29 19:45:50 +00:00
version = "0.99.17"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" to get latest versions. Also fix a couple of warnings introduced by now-unneeded imports with new ed25519 crate. This is part of the process for releasing our next version.
2021-11-29 19:45:50 +00:00
checksum = "4fb810d30a7c1953f91334de7244731fc3f3c10d7fe163338a35b9f640960321"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"convert_case",
"proc-macro2",
"quote",
Run "cargo update" to get latest versions. Also fix a couple of warnings introduced by now-unneeded imports with new ed25519 crate. This is part of the process for releasing our next version.
2021-11-29 19:45:50 +00:00
"rustc_version",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "digest"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d3dd60d1080a57a05ab032377049e0591415d2b31afd7028356dbf3cc6dcb066"
dependencies = [
"generic-array",
]
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
[[package]]
name = "digest"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.10.7"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "9ed9a281f7bc9b7576e61468ba615a66a5c8cfdff42420a70aa82701a3b1e292"
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
dependencies = [
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
"block-buffer 0.10.4",
Upgrade rsa to 0.7. Closes #613.
2022-10-28 18:38:42 +01:00
"const-oid",
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
"crypto-common",
"subtle",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "directories"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "5.0.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "9a49173b84e034382284f27f1af4dcbbd231ffa358c0fe316541a7337f376a35"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Update to shellexpand 3.1.0 so we can use dirs 5 everywhere Results of precisely cargo update -p shellexpand Incorporates changes I have made to shellexpand to allow use of dirs 4 *or* dirs 5.
2023-03-24 11:30:14 +00:00
"dirs-sys",
Bump to the lastest versions of dirs and directories.
2023-03-22 19:15:42 +00:00
]
[[package]]
name = "dirs"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "5.0.1"
Bump to the lastest versions of dirs and directories.
2023-03-22 19:15:42 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "44c45a9d03d6676652bcb5e724c7e988de1acad23a711b5217ab9cbecbec2225"
Bump to the lastest versions of dirs and directories.
2023-03-22 19:15:42 +00:00
dependencies = [
Update to shellexpand 3.1.0 so we can use dirs 5 everywhere Results of precisely cargo update -p shellexpand Incorporates changes I have made to shellexpand to allow use of dirs 4 *or* dirs 5.
2023-03-24 11:30:14 +00:00
"dirs-sys",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Bump to the lastest versions of dirs and directories.
2023-03-22 19:15:42 +00:00
[[package]]
name = "dirs-sys"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.4.1"
Bump to the lastest versions of dirs and directories.
2023-03-22 19:15:42 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "520f05a5cbd335fae5a99ff7a6ab8627577660ee5cfd6a94a6a929b52ff0321c"
Bump to the lastest versions of dirs and directories.
2023-03-22 19:15:42 +00:00
dependencies = [
"libc",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"option-ext",
Bump to the lastest versions of dirs and directories.
2023-03-22 19:15:42 +00:00
"redox_users",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"windows-sys 0.48.0",
Bump to the lastest versions of dirs and directories.
2023-03-22 19:15:42 +00:00
]
netdoc: add a new type for Nicknames Relay nicknames are always between 1 and 19 characters long, and they're always ASCII: That means that storing them in a [u8;19] will always be possible, and always use less resources than storing them in a String. Fortunately, the tinystr crate already helps us with this kind of thing.
2022-03-10 21:38:23 +00:00
[[package]]
name = "displaydoc"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.2.4"
netdoc: add a new type for Nicknames Relay nicknames are always between 1 and 19 characters long, and they're always ASCII: That means that storing them in a [u8;19] will always be possible, and always use less resources than storing them in a String. Fortunately, the tinystr crate already helps us with this kind of thing.
2022-03-10 21:38:23 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "487585f4d0c6655fe74905e2504d8ad6908e4db67f744eb140876906c2f3175d"
netdoc: add a new type for Nicknames Relay nicknames are always between 1 and 19 characters long, and they're always ASCII: That means that storing them in a [u8;19] will always be possible, and always use less resources than storing them in a String. Fortunately, the tinystr crate already helps us with this kind of thing.
2022-03-10 21:38:23 +00:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
netdoc: add a new type for Nicknames Relay nicknames are always between 1 and 19 characters long, and they're always ASCII: That means that storing them in a [u8;19] will always be possible, and always use less resources than storing them in a String. Fortunately, the tinystr crate already helps us with this kind of thing.
2022-03-10 21:38:23 +00:00
]
use downcast-rs instead of our own AsAny
2022-03-12 10:10:00 +00:00
[[package]]
name = "downcast-rs"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9ea835d29036a4087793836fa931b08837ad5e957da9e23886b29586fb9b6650"
replace Arc with Box and use dyn-clone this also removes JoinResult
2022-03-12 17:33:25 +00:00
[[package]]
name = "dyn-clone"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "1.0.11"
replace Arc with Box and use dyn-clone this also removes JoinResult
2022-03-12 17:33:25 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "68b0cf012f1230e43cd00ebb729c6bb58707ecfa8ad08b52ef3a4ccd2697fc30"
replace Arc with Box and use dyn-clone this also removes JoinResult
2022-03-12 17:33:25 +00:00
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "ecdsa"
version = "0.14.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "413301934810f597c1d19ca71c8710e99a3f1ba28a0d2ebc01551a2daeea3c5c"
dependencies = [
"der 0.6.1",
"elliptic-curve",
"rfc6979",
"signature 1.6.4",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "ed25519"
Bump Cargo.lock to ed25519 1.5.3 to fix CI. ed25519 1.5.2 has been yanked.
2023-01-16 16:39:35 +00:00
version = "1.5.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Cargo.lock to ed25519 1.5.3 to fix CI. ed25519 1.5.2 has been yanked.
2023-01-16 16:39:35 +00:00
checksum = "91cff35c70bba8a626e3185d8cd48cc11b5437e1a5bcd15b9b5fa3c64b6dfee7"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Upgrade to latest rsa crate.
2023-01-19 20:22:18 +00:00
"signature 1.6.4",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "ed25519-dalek"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c762bae6dcaf24c4c84667b8579785430908723d5c889f469d76a41d59cc7a9d"
dependencies = [
Back down x25519-dalek to 2.0.0-pre.1 from 2.0.0-rc.2 ========================= Notes from nickm: (This differs from pinkforest's original MR: It removes the Cargo.lock changes and the version bump on tor-llcrypto.) Minimal Cargo.lock changes from downgrade. (These are exactly those changes generated by running "build" and "test".) There are several reasons to do this: * It's best to bump all of our dalek dependencies at once to rc.3 or later, rather than the piecemeal approach we've been stuck with so far. * We don't want to do this bump right now, since there are some tricky questions about clamping we need to figure out (see #808), and we need to make sure we get them right, and we're in a distracted this week. * We _do_ need to move away from 2.0.0-rc.2 right now, since it was causing a failure in `cargo install arti`, and then it got yanked. Thanks to pinkforest for helping us out here and explaining all of this! Fixes #926. Commit-edited-by: Nick Mathewson <nickm@torproject.org>
2023-06-27 01:45:36 +01:00
"curve25519-dalek",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"ed25519",
"merlin",
"rand 0.7.3",
"serde",
Run "cargo update".
2022-01-11 14:27:22 +00:00
"sha2 0.9.9",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"zeroize",
]
Import educe into tor-bytes and provide skip_fmt Preparatory work for getting rid of some manual Debug impls
2022-03-02 14:32:12 +00:00
[[package]]
name = "educe"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
version = "0.4.22"
Import educe into tor-bytes and provide skip_fmt Preparatory work for getting rid of some manual Debug impls
2022-03-02 14:32:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
checksum = "079044df30bb07de7d846d41a184c4b00e66ebdac93ee459253474f3a47e50ae"
Import educe into tor-bytes and provide skip_fmt Preparatory work for getting rid of some manual Debug impls
2022-03-02 14:32:12 +00:00
dependencies = [
"enum-ordinalize",
"proc-macro2",
"quote",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
Import educe into tor-bytes and provide skip_fmt Preparatory work for getting rid of some manual Debug impls
2022-03-02 14:32:12 +00:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "either"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "1.8.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "7fcaabb2fef8c910e7f4c7ce9f67a1283a1715879a7c230ca9d6d1ae31f16d91"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "elliptic-curve"
version = "0.12.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e7bb888ab5300a19b8e5bceef25ac745ad065f3c9f7efc6de1b91958110891d3"
dependencies = [
"base16ct",
"crypto-bigint",
"der 0.6.1",
"digest 0.10.7",
"ff",
"generic-array",
"group",
"rand_core 0.6.4",
"sec1",
"subtle",
"zeroize",
]
actually add DNS support
2022-03-06 19:44:50 +00:00
[[package]]
name = "enum-as-inner"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
version = "0.5.1"
actually add DNS support
2022-03-06 19:44:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
checksum = "c9720bba047d567ffc8a3cba48bf19126600e249ab7f128e9233e6376976a116"
actually add DNS support
2022-03-06 19:44:50 +00:00
dependencies = [
"heck",
"proc-macro2",
"quote",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
actually add DNS support
2022-03-06 19:44:50 +00:00
]
Import educe into tor-bytes and provide skip_fmt Preparatory work for getting rid of some manual Debug impls
2022-03-02 14:32:12 +00:00
[[package]]
name = "enum-ordinalize"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "3.1.13"
Import educe into tor-bytes and provide skip_fmt Preparatory work for getting rid of some manual Debug impls
2022-03-02 14:32:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "e4f76552f53cefc9a7f64987c3701b99d982f7690606fd67de1d09712fbf52f1"
Import educe into tor-bytes and provide skip_fmt Preparatory work for getting rid of some manual Debug impls
2022-03-02 14:32:12 +00:00
dependencies = [
"num-bigint",
"num-traits",
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
Import educe into tor-bytes and provide skip_fmt Preparatory work for getting rid of some manual Debug impls
2022-03-02 14:32:12 +00:00
]
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
[[package]]
name = "env_logger"
version = "0.5.13"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "15b0a4d2e39f8420210be8b27eeda28029729e2fd4291019455016c348240c38"
dependencies = [
"atty",
"humantime 1.3.0",
"log",
"regex",
"termcolor",
]
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
[[package]]
name = "equivalent"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "88bffebc5d80432c9b140ee17875ff173a8ab62faad5b257da912bd2f6c1c0a1"
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
[[package]]
name = "erased-serde"
version = "0.3.25"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4f2b0c2380453a92ea8b6c8e5f64ecaafccddde8ceab55ff7a8ac1029f894569"
dependencies = [
"serde",
]
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
[[package]]
name = "errno"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "0.3.1"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "4bcfec3a70f97c962c307b2d2c56e358cf1d00b558d74262b5f929ee8cc7e73a"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
dependencies = [
"errno-dragonfly",
"libc",
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
"windows-sys 0.48.0",
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
]
[[package]]
name = "errno-dragonfly"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aa68f1b12764fab894d2755d2518754e71b4fd80ecfb822714a1206c2aab39bf"
dependencies = [
"cc",
"libc",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "event-listener"
Run "cargo update" in preparation for next week's release.
2022-07-27 14:27:30 +01:00
version = "2.5.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for next week's release.
2022-07-27 14:27:30 +01:00
checksum = "0206175f82b8d6bf6652ff7d71a1e27fd2e4efde587fd368662814d6ec1d9ce0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "fallible-iterator"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4443176a9f2c162692bd3d352d745ef9413eec5782a80d8fd6f8a1ac692a07f7"
[[package]]
name = "fallible-streaming-iterator"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7360491ce676a36bf9bb3c56c1aa791658183a54d2744120f27285738d90465a"
[[package]]
name = "fastrand"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
version = "1.9.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
checksum = "e51093e27b0797c359783294ca4f0a911c270184cb10f85783b118614a1501be"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"instant",
]
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "ff"
version = "0.12.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d013fc25338cc558c5c2cfbad646908fb23591e2404481826742b651c9af7160"
dependencies = [
"rand_core 0.6.4",
"subtle",
]
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
[[package]]
name = "filetime"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "0.2.21"
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "5cbc844cecaee9d4443931972e1289c8ff485cb4cc2767cb03ca139ed6885153"
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
"libc",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"redox_syscall 0.2.16",
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
"windows-sys 0.48.0",
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "flate2"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
version = "1.0.26"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
checksum = "3b9429470923de8e8cbd4d2dc513535400b4b3fef0319fb5c4e1f520a7bef743"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"crc32fast",
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
"miniz_oxide 0.7.1",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
update misc/Cargo.lock
2021-09-12 09:28:00 +01:00
[[package]]
name = "float-cmp"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "98de4bbd547a563b716d8dfa9aad1cb19bfab00f4fa09a6a4ed21dbcf44ce9c4"
dependencies = [
"num-traits",
]
arti-bench: add support for multiple samples & averaging We now do multiple samples (configurable; default 3) per type of `arti-bench` benchmark run, and take a mean and median average of all data collected, in order to hopefully be a bit more resilient to random outliers / variation. This uses some `futures::stream::Stream` hacks, which might result in more connections being made than required (and might impact the TTFB metrics somewhat, at least for downloading). Results now get collected into a `BenchmarkResults` struct per type of benchmark, which will be in turn placed into a `BenchmarkSummary` in a later commit; this will also add the ability to serialize the latter struct out to disk, for future reference. part of arti#292
2022-01-13 16:23:11 +00:00
[[package]]
name = "float-ord"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8ce81f49ae8a0482e4c55ea62ebbd7e5a686af544c00b9d090bba3ff9be97b3d"
tor-dirmgr: Create a bootstrap-status exporting mechanism. The interface is similar to the one exposed by `arti-client`: it internally uses postage::watch to give a series of events showing when a bootstrap status is changing. Thanks to the existing state/driver separation in the DirMgr design we don't need much new logic: each download state needs to expose (internally) how far along it is in its download, which the bootstrap code passes to the DirMgr if it has changed. I believe that in the long run, we'll probably want to expose more (or different) information here, and we'll want to process it differently. With that in mind, I've made the API for `DirBootstrapStatus` deliberately narrow, so that we can change its of its internal later on without breaking code that depends on it. (The information exposed by this commit is not yet summarized in `arti-client`.) Part of #96.
2022-01-13 18:55:34 +00:00
[[package]]
name = "float_eq"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
version = "1.0.1"
tor-dirmgr: Create a bootstrap-status exporting mechanism. The interface is similar to the one exposed by `arti-client`: it internally uses postage::watch to give a series of events showing when a bootstrap status is changing. Thanks to the existing state/driver separation in the DirMgr design we don't need much new logic: each download state needs to expose (internally) how far along it is in its download, which the bootstrap code passes to the DirMgr if it has changed. I believe that in the long run, we'll probably want to expose more (or different) information here, and we'll want to process it differently. With that in mind, I've made the API for `DirBootstrapStatus` deliberately narrow, so that we can change its of its internal later on without breaking code that depends on it. (The information exposed by this commit is not yet summarized in `arti-client`.) Part of #96.
2022-01-13 18:55:34 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
checksum = "28a80e3145d8ad11ba0995949bbcf48b9df2be62772b3d351ef017dff6ecb853"
tor-dirmgr: Create a bootstrap-status exporting mechanism. The interface is similar to the one exposed by `arti-client`: it internally uses postage::watch to give a series of events showing when a bootstrap status is changing. Thanks to the existing state/driver separation in the DirMgr design we don't need much new logic: each download state needs to expose (internally) how far along it is in its download, which the bootstrap code passes to the DirMgr if it has changed. I believe that in the long run, we'll probably want to expose more (or different) information here, and we'll want to process it differently. With that in mind, I've made the API for `DirBootstrapStatus` deliberately narrow, so that we can change its of its internal later on without breaking code that depends on it. (The information exposed by this commit is not yet summarized in `arti-client`.) Part of #96.
2022-01-13 18:55:34 +00:00
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
[[package]]
name = "fluid-let"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "749cff877dc1af878a0b31a41dd221a753634401ea0ef2f87b62d3171522485a"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "fnv"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
[[package]]
name = "foreign-types"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f6f339eb8adc052cd2ca78910fda869aefa38d22d5cb648e6485e4d3fc06f3b1"
dependencies = [
"foreign-types-shared",
]
[[package]]
name = "foreign-types-shared"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "00b0228411908ca8685dba7fc2cdd70ec9990a6e753e89b6ac91a84c40fbaf4b"
[[package]]
name = "form_urlencoded"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "1.2.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "a62bc1cf6f830c2ec14a513a9fb124d0a213a629668a4186f329db21fe045652"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"percent-encoding",
]
Second cut at a fs-mistrust crate. This crate is meant to solve #315 by giving a way to make sure that a file or directory is only accessible by trusted users. I've tried to explain carefully (in comments and documentation) what this crate is doing and why, under the assumption that it will someday be read by another person like me who does _not_ live and breathe unix file permissions. The crate is still missing some key features, noted in the TODO section. It differs from the first version of the crate by taking a more principled approach to directory checking: it emulates the path lookup process (reading symlinks and all) one path change at a time, thus ensuring that we check every directory which could enable an untrusted user to get to our target file, _or_ which could enable them to get to any symlink that would get them to the target file. The API is also slightly different: It separates the `Mistrust` object (where you configure what you do or do not trust) from the `Verifier` (where you set up a check that you want to perform on a single object). Verifiers are set up to be a bit ephemeral, so that it is hard to accidentally declare that _every_ object is meant to be readable when you only mean that _some_ objects may be readable.
2022-04-13 16:32:23 +01:00
[[package]]
name = "fs-mistrust"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.7.2"
Second cut at a fs-mistrust crate. This crate is meant to solve #315 by giving a way to make sure that a file or directory is only accessible by trusted users. I've tried to explain carefully (in comments and documentation) what this crate is doing and why, under the assumption that it will someday be read by another person like me who does _not_ live and breathe unix file permissions. The crate is still missing some key features, noted in the TODO section. It differs from the first version of the crate by taking a more principled approach to directory checking: it emulates the path lookup process (reading symlinks and all) one path change at a time, thus ensuring that we check every directory which could enable an untrusted user to get to our target file, _or_ which could enable them to get to any symlink that would get them to the target file. The API is also slightly different: It separates the `Mistrust` object (where you configure what you do or do not trust) from the `Verifier` (where you set up a check that you want to perform on a single object). Verifiers are set up to be a bit ephemeral, so that it is hard to accidentally declare that _every_ object is meant to be readable when you only mean that _some_ objects may be readable.
2022-04-13 16:32:23 +01:00
dependencies = [
fs-mistrust: make Mistrust have a corresponding Builder type. This is an approximately minimal revision to get Builder in place; subsequent commits will clean up the API.
2022-05-18 18:26:01 +01:00
"derive_builder_fork_arti",
Update to shellexpand 3.1.0 so we can use dirs 5 everywhere Results of precisely cargo update -p shellexpand Incorporates changes I have made to shellexpand to allow use of dirs 4 *or* dirs 5.
2023-03-24 11:30:14 +00:00
"dirs",
fs-mistrust: Add Group and User types. This will help make the actual configuration more serializable, I hope.
2022-05-18 19:36:24 +01:00
"educe",
Second cut at a fs-mistrust crate. This crate is meant to solve #315 by giving a way to make sure that a file or directory is only accessible by trusted users. I've tried to explain carefully (in comments and documentation) what this crate is doing and why, under the assumption that it will someday be read by another person like me who does _not_ live and breathe unix file permissions. The crate is still missing some key features, noted in the TODO section. It differs from the first version of the crate by taking a more principled approach to directory checking: it emulates the path lookup process (reading symlinks and all) one path change at a time, thus ensuring that we check every directory which could enable an untrusted user to get to our target file, _or_ which could enable them to get to any symlink that would get them to the target file. The API is also slightly different: It separates the `Mistrust` object (where you configure what you do or do not trust) from the `Verifier` (where you set up a check that you want to perform on a single object). Verifiers are set up to be a bit ephemeral, so that it is hard to accidentally declare that _every_ object is meant to be readable when you only mean that _some_ objects may be readable.
2022-04-13 16:32:23 +01:00
"libc",
fs-mistrust: Add code to make a self-named group "trusted". This required a bit of poking through the `users` crate, to mess with the user and group dbs. The original goal was to "trust the group with the same name as us", but it turned into a bit of a production, since: * We want to take our own name from $USER, assuming that matches our uid. (Otherwise we want to ask getpwuid_r().) * We only want to trust the group if we are actually a member of that group. * We want to cache this information. * We want to test this code.
2022-04-27 20:20:56 +01:00
"once_cell",
Add serde derives for MistrustBuilder. The Group and User (de)serialization is pretty ugly, and I can't vouch for the correcness of MistrustBuilder. I will seek feedback before I proceed.
2022-05-18 21:29:23 +01:00
"serde",
Write custom serde impls for Trusted{User,Group} We support all of the following (in TOML notation): ``` user = "rose" # by name user = 413 # by ID user = false # no user user = ":current" # A 'special' user. user = { name: "rose" } user = { id: 413 } user = { special: ":none" } user = { special: ":current" } ```
2022-05-20 20:15:56 +01:00
"serde_json",
Second cut at a fs-mistrust crate. This crate is meant to solve #315 by giving a way to make sure that a file or directory is only accessible by trusted users. I've tried to explain carefully (in comments and documentation) what this crate is doing and why, under the assumption that it will someday be read by another person like me who does _not_ live and breathe unix file permissions. The crate is still missing some key features, noted in the TODO section. It differs from the first version of the crate by taking a more principled approach to directory checking: it emulates the path lookup process (reading symlinks and all) one path change at a time, thus ensuring that we check every directory which could enable an untrusted user to get to our target file, _or_ which could enable them to get to any symlink that would get them to the target file. The API is also slightly different: It separates the `Mistrust` object (where you configure what you do or do not trust) from the `Verifier` (where you set up a check that you want to perform on a single object). Verifiers are set up to be a bit ephemeral, so that it is hard to accidentally declare that _every_ object is meant to be readable when you only mean that _some_ objects may be readable.
2022-04-13 16:32:23 +01:00
"tempfile",
"thiserror",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"toml 0.7.5",
fs-mistrust: Add code to make a self-named group "trusted". This required a bit of poking through the `users` crate, to mess with the user and group dbs. The original goal was to "trust the group with the same name as us", but it turned into a bit of a production, since: * We want to take our own name from $USER, assuming that matches our uid. (Otherwise we want to ask getpwuid_r().) * We only want to trust the group if we are actually a member of that group. * We want to cache this information. * We want to test this code.
2022-04-27 20:20:56 +01:00
"users",
Add functionality to inspect directory content permissions Also, explain _why_ this is pretty important.
2022-04-19 01:23:23 +01:00
"walkdir",
Second cut at a fs-mistrust crate. This crate is meant to solve #315 by giving a way to make sure that a file or directory is only accessible by trusted users. I've tried to explain carefully (in comments and documentation) what this crate is doing and why, under the assumption that it will someday be read by another person like me who does _not_ live and breathe unix file permissions. The crate is still missing some key features, noted in the TODO section. It differs from the first version of the crate by taking a more principled approach to directory checking: it emulates the path lookup process (reading symlinks and all) one path change at a time, thus ensuring that we check every directory which could enable an untrusted user to get to our target file, _or_ which could enable them to get to any symlink that would get them to the target file. The API is also slightly different: It separates the `Mistrust` object (where you configure what you do or do not trust) from the `Verifier` (where you set up a check that you want to perform on a single object). Verifiers are set up to be a bit ephemeral, so that it is hard to accidentally declare that _every_ object is meant to be readable when you only mean that _some_ objects may be readable.
2022-04-13 16:32:23 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "fslock"
Run "cargo update".
2022-01-11 14:27:22 +00:00
version = "0.2.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2022-01-11 14:27:22 +00:00
checksum = "04412b8935272e3a9bae6f48c7bfff74c2911f60525404edfdd28e49884c3bfb"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"libc",
update to v5.0.0
2022-08-12 19:50:08 +01:00
"winapi",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "futures"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.3.28"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "23342abe12aba583913b2e62f22225ff9c950774065e4bfb61a19cd9770fec40"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"futures-channel",
"futures-core",
"futures-executor",
"futures-io",
"futures-sink",
"futures-task",
"futures-util",
]
[[package]]
name = "futures-await-test"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ae0d3d05bce73a572ba581e4f4a7f20164c18150169c3a67f406aada3e48c7e8"
dependencies = [
"futures-await-test-macro",
"futures-executor",
]
[[package]]
name = "futures-await-test-macro"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4f150175e6832600500334550e00e4dc563a0b32f58a9d1ad407f6473378c839"
dependencies = [
"proc-macro2",
"quote",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "futures-channel"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.3.28"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "955518d47e09b25bbebc7a18df10b81f0c766eaf4c4f1cccef2fca5f2a4fb5f2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"futures-core",
"futures-sink",
]
[[package]]
name = "futures-core"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.3.28"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "4bca583b7e26f571124fe5b7561d49cb2868d79116cfa0eefce955557c6fee8c"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "futures-executor"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.3.28"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "ccecee823288125bd88b4d7f565c9e58e41858e47ab72e8ea2d64e93624386e0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"futures-core",
"futures-task",
"futures-util",
]
[[package]]
name = "futures-io"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.3.28"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "4fff74096e71ed47f8e023204cfd0aa1289cd54ae5430a9523be060cdb849964"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "futures-lite"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "1.13.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "49a9d51ce47660b1e808d3c990b4709f2f415d928835a17dfd16991515c46bce"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"fastrand",
"futures-core",
"futures-io",
"memchr",
"parking",
"pin-project-lite",
"waker-fn",
]
[[package]]
name = "futures-macro"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.3.28"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "89ca545a94061b6365f2c7355b4b32bd20df3ff95f02da9329b34ccc3bd6ee72"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "futures-sink"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.3.28"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "f43be4fe21a13b9781a69afa4985b0f6ee0e1afab2c6f454a8cf30e2b2237b6e"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "futures-task"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.3.28"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "76d3d132be6c0e6aa1534069c705a74a5997a356c0dc2f86a47765e5617c5b65"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "futures-util"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.3.28"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "26b01e40b772d54cf6c6d721c1d1abd0647a0106a12ecaa1c186273392a69533"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"futures-channel",
"futures-core",
"futures-io",
"futures-macro",
"futures-sink",
"futures-task",
"memchr",
"pin-project-lite",
"pin-utils",
"slab",
]
rpc: Remove fake_generational_arena Now that generation-arena has merged [@diziet's patch] to clarify their license, we no longer need to disable it. [@diziet's patch]: https://github.com/fitzgen/generational-arena/pull/56
2023-05-23 18:55:23 +01:00
[[package]]
name = "generational-arena"
version = "0.2.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "877e94aff08e743b651baaea359664321055749b398adff8740a7399af7796e7"
dependencies = [
"cfg-if",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "generic-array"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.14.7"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "85649ca51fd72272d7821adaf274ad91c288277713d9c18820d8499a7ff69e9a"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"typenum",
"version_check",
]
[[package]]
name = "getrandom"
version = "0.1.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8fc3cb4d91f53b50155bdcfd23f6a4c39ae1969c2ae85982b135750cccaf5fce"
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"libc",
"wasi 0.9.0+wasi-snapshot-preview1",
]
[[package]]
name = "getrandom"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.2.10"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "be4136b2a15dd319360be1c07d9933517ccf0be8f16bf62a3bee4f0d618df427"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
Update misc/Cargo.lock.
2021-09-17 13:11:39 +01:00
"js-sys",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"libc",
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
"wasi 0.11.0+wasi-snapshot-preview1",
Update misc/Cargo.lock.
2021-09-17 13:11:39 +01:00
"wasm-bindgen",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
[[package]]
name = "ghost"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e77ac7b51b8e6313251737fcef4b1c01a2ea102bde68415b62c0ee9268fec357"
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
]
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
[[package]]
name = "gimli"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.27.3"
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "b6c80984affa11d98d1b88b66ac8853f143217b399d3c74116778ff8fdb4ed2e"
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "gloo-timers"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "0.2.6"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "9b995a66bb87bebce9a0f4a95aed01daca4872c050bfcb21653361c03bc35e5c"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"futures-channel",
"futures-core",
"js-sys",
"wasm-bindgen",
]
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "group"
version = "0.12.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5dfbfb3a6cfbd390d5c9564ab283a0349b9b9fcd46a706c1eb10e0db70bfbac7"
dependencies = [
"ff",
"rand_core 0.6.4",
"subtle",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "hashbrown"
Bump to rusqlite 0.28.
2022-07-19 21:41:50 +01:00
version = "0.12.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump to rusqlite 0.28.
2022-07-19 21:41:50 +01:00
checksum = "8a9ee70c43aaf417c914396645a0fa852624801b24ebb7ae78fe8272889ac888"
Run "cargo update".
2023-05-22 12:47:20 +01:00
[[package]]
name = "hashbrown"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.14.0"
Run "cargo update".
2023-05-22 12:47:20 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "2c6201b9ff9fd90a5a3bac2e56a830d0caa509576f0e503818ee82c181b3437a"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"ahash",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"allocator-api2",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "hashlink"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.8.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "312f66718a2d7789ffef4f4b7b213138ed9f1eb3aa1d0d82fc99f88fb3ffd26f"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"hashbrown 0.14.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
actually add DNS support
2022-03-06 19:44:50 +00:00
[[package]]
name = "heck"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
version = "0.4.1"
actually add DNS support
2022-03-06 19:44:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
checksum = "95505c38b4572b2d910cecb0281560f54b440a19336cbbcb27bf6ce6adc6f5a8"
actually add DNS support
2022-03-06 19:44:50 +00:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "hermit-abi"
version = "0.1.19"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "62b467343b94ba476dcb2500d242dadbb39557df889310ac77c5d99100aaac33"
dependencies = [
"libc",
]
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
[[package]]
name = "hermit-abi"
version = "0.2.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ee512640fe35acbfb4bb779db6f0d80704c2cacfa2e39b601ef3e3f47d1ae4c7"
dependencies = [
"libc",
]
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
[[package]]
name = "hermit-abi"
fix audit
2023-07-04 19:57:25 +01:00
version = "0.3.2"
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
fix audit
2023-07-04 19:57:25 +01:00
checksum = "443144c8cdadd93ebf52ddb4056d257f5b52c04d3c804e657d19eb73fc33668b"
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "hex"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7f24254aa9a54b5c858eaee2f5bccdb46aaf0e486a595ed5fd8f86ba55232a70"
[[package]]
name = "hex-literal"
Upgrade our hex-literal dependency
2023-04-13 12:51:26 +01:00
version = "0.4.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade our hex-literal dependency
2023-04-13 12:51:26 +01:00
checksum = "6fe2267d4ed49bc07b63801559be28c718ea06c4738b7a03c94df7386d2cde46"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "hkdf"
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
version = "0.12.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
checksum = "791a029f6b9fc27657f6f188ec6e5e43f6911f6f878e0dc5501396e09809d437"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"hmac",
]
[[package]]
name = "hmac"
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
version = "0.12.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
checksum = "6c49c37c09c17a53d937dfbb742eb3a961d65a994e6bcdcf37e7399d0cc8ab5e"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Use hostname-validator crate for hostname validation
2022-09-22 14:48:51 +01:00
[[package]]
name = "hostname-validator"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f558a64ac9af88b5ba400d99b579451af0d39c6d360980045b91aac966d705e2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "http"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
version = "0.2.9"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
checksum = "bd6effc99afb63425aff9b05836f029929e345a6148a14b7ecd5ab67af944482"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"bytes",
"fnv",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"itoa",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
[[package]]
name = "http-body"
Run "cargo update" in preparation for the next release.
2022-05-24 20:08:01 +01:00
version = "0.4.5"
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for the next release.
2022-05-24 20:08:01 +01:00
checksum = "d5f38f16d184e36f2408a55281cd658ecbd3ca05cce6d6510a176eca393e26d1"
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
dependencies = [
"bytes",
"http",
"pin-project-lite",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "httparse"
Run cargo update again, in preparation for release
2022-08-31 16:09:26 +01:00
version = "1.8.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update again, in preparation for release
2022-08-31 16:09:26 +01:00
checksum = "d897f394bad6a705d5f4104762e116a75639e470d80901eed05a860a95cb1904"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "httpdate"
update dependencies
2021-11-17 19:17:08 +00:00
version = "1.0.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update dependencies
2021-11-17 19:17:08 +00:00
checksum = "c4a1e36c821dbe04574f602848a19f742f4fb3c98d40449f11bcad18d6b17421"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
[[package]]
name = "humantime"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "df004cfca50ef23c36850aaaa59ad52cc70d0e90243c3c7737a4dd32dc7a3c4f"
dependencies = [
"quick-error",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "humantime"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9a3a5bfb195931eeb336b2a7b4d761daec841b97f947d34394601737a7bba5e4"
[[package]]
name = "humantime-serde"
humantime: Update to humantime-serde 1.1.1 This has the humantime_serde::option module, which we have upstreamed and are about to switch to. The remaining dependency with version = "1" is going to be removed in a moment.
2022-03-11 17:24:21 +00:00
version = "1.1.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
humantime: Update to humantime-serde 1.1.1 This has the humantime_serde::option module, which we have upstreamed and are about to switch to. The remaining dependency with version = "1" is going to be removed in a moment.
2022-03-11 17:24:21 +00:00
checksum = "57a3db5ea5923d99402c94e9feb261dc5ee9b4efa158b0315f788cf549cc200c"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
"humantime 2.1.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"serde",
]
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
[[package]]
name = "hyper"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.14.27"
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "ffb1cfd654a8219eaef89881fdb3bb3b1cdc5fa75ded05d6933b2b382e395468"
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
dependencies = [
"bytes",
"futures-channel",
"futures-core",
"futures-util",
"http",
"http-body",
"httparse",
"httpdate",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"itoa",
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
"pin-project-lite",
"socket2",
"tokio",
"tower-service",
"tracing",
"want",
]
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
[[package]]
name = "iana-time-zone"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.1.57"
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "2fad5b825842d2b38bd206f3e81d6957625fd7f0a361e345c30e01a0ae2dd613"
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
dependencies = [
"android_system_properties",
"core-foundation-sys",
"iana-time-zone-haiku",
"js-sys",
"wasm-bindgen",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"windows",
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
]
[[package]]
name = "iana-time-zone-haiku"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.1.2"
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "f31827a206f56af32e590ba56d5d2d085f558508192593743f16b2306495269f"
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
dependencies = [
Run "cargo update".
2023-05-22 12:47:20 +01:00
"cc",
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "ident_case"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b9e0384b61958566e926dc50660321d12159025e767c18e043daf26b70104c39"
[[package]]
name = "idna"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "418a0a6fab821475f634efe3ccc45c013f742efe03d853e8d3355d5cb850ecf8"
dependencies = [
"matches",
"unicode-bidi",
"unicode-normalization",
]
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
[[package]]
name = "idna"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.4.0"
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "7d20d6b07bfbc108882d88ed8e37d39636dcc260e15e30c45e6ba089610b917c"
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
dependencies = [
"unicode-bidi",
"unicode-normalization",
]
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
[[package]]
name = "indexmap"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "1.9.3"
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "bd070e393353796e801d209ad339e89596eb4c8d430d18ede6a1cced8fafbd99"
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
dependencies = [
"autocfg",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"hashbrown 0.12.3",
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
"serde",
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
]
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
[[package]]
name = "indexmap"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d5477fe2230a79769d8dc68e0eabf5437907c0457a5614a9e8dddb67f65eb65d"
dependencies = [
"equivalent",
"hashbrown 0.14.0",
]
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
[[package]]
name = "inotify"
update to v5.0.0
2022-08-12 19:50:08 +01:00
version = "0.9.6"
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update to v5.0.0
2022-08-12 19:50:08 +01:00
checksum = "f8069d3ec154eb856955c1c0fbffefbf5f3c40a104ec912d4797314c1801abff"
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
dependencies = [
Upgrade to bitflags 2.0 This version of bitflags now requires us to explicitly list the traits that we want to derive for our bit-flags structs.
2023-03-13 12:47:14 +00:00
"bitflags 1.3.2",
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
"inotify-sys",
"libc",
]
[[package]]
name = "inotify-sys"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e05c02b5e89bff3b946cedeca278abc628fe811e604f027c45a8aa3cf793d0eb"
dependencies = [
"libc",
]
Upgrade to AES 0.8 Now that we require Rust 1.56, we can upgrade to AES 0.8. This forces us to have some slight API changes. We require cipher 0.4.1, not cipher 0.4.0, since 0.4.0 has compatibility issues with Rust 1.56.
2022-04-25 20:39:26 +01:00
[[package]]
name = "inout"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a0c10553d664a4d0bcff9f4215d0aac67a639cc68ef660840afe309b807bc9f5"
dependencies = [
"generic-array",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "instant"
Update Cargo.lock in preparation for Arti 0.0.1 release.
2021-10-29 14:40:35 +01:00
version = "0.1.12"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update Cargo.lock in preparation for Arti 0.0.1 release.
2021-10-29 14:40:35 +01:00
checksum = "7a5bbe824c507c5da5956355e86a746d82e0e1464f65d862cc5e71da70e94b2c"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
[[package]]
name = "inventory"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.3.6"
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "e0539b5de9241582ce6bd6b0ba7399313560151e58c9aaf8b74b711b1bdce644"
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
dependencies = [
"ghost",
]
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
[[package]]
name = "io-lifetimes"
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
version = "1.0.11"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
checksum = "eae7b9aee968036d54dce06cebaefd919e4472e753296daccd6d344e3e2df0c2"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
dependencies = [
fix audit
2023-07-04 19:57:25 +01:00
"hermit-abi 0.3.2",
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
"libc",
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
"windows-sys 0.48.0",
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
]
actually add DNS support
2022-03-06 19:44:50 +00:00
[[package]]
name = "ipnet"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "2.8.0"
actually add DNS support
2022-03-06 19:44:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "28b29a3cd74f0f4598934efe3aeba42bae0eb4680554128851ebbecb02af14e6"
actually add DNS support
2022-03-06 19:44:50 +00:00
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
[[package]]
name = "itertools"
version = "0.10.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b0fd2260e829bddf4cb6ea802289de2f86d6a7a690192fbe91b3f46e0f2c8473"
dependencies = [
"either",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "itertools"
Upgrade to itertools 0.11.0 The breaking changes here do not seem to affect us.
2023-06-26 14:30:54 +01:00
version = "0.11.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade to itertools 0.11.0 The breaking changes here do not seem to affect us.
2023-06-26 14:30:54 +01:00
checksum = "b1c173a5686ce8bfa551b3563d0c2170bf24ca44da99c7ca4bfdab5418c3fe57"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"either",
]
Run "cargo update".
2022-01-11 14:27:22 +00:00
[[package]]
name = "itoa"
Upgrade dependency to latest rusqlite.
2023-03-30 13:33:44 +01:00
version = "1.0.6"
Run "cargo update".
2022-01-11 14:27:22 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependency to latest rusqlite.
2023-03-30 13:33:44 +01:00
checksum = "453ad9f582a441959e5f0d088b02ce04cfe8d51a8eaf077f12ac6d3e94164ca6"
Run "cargo update".
2022-01-11 14:27:22 +00:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "jobserver"
Update required openssl version cargo-audit is complaining about 0.10.45.
2023-03-24 12:02:59 +00:00
version = "0.1.26"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update required openssl version cargo-audit is complaining about 0.10.45.
2023-03-24 12:02:59 +00:00
checksum = "936cfd212a0155903bcbc060e316fb6cc7cbf2e1907329391ebadc1fe0ce77c2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"libc",
]
[[package]]
name = "js-sys"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.3.64"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "c5f195fe497f702db0f318b07fdd68edb16955aed830df8363d837542f8f935a"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"wasm-bindgen",
]
[[package]]
name = "keccak"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.1.4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "8f6d5ed8676d904364de097082f4e7d240b571b67989ced0240f08b7f966f940"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
dependencies = [
"cpufeatures",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
[[package]]
update to v5.0.0
2022-08-12 19:50:08 +01:00
name = "kqueue"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
version = "1.0.7"
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
checksum = "2c8fc60ba15bf51257aa9807a48a61013db043fcf3a78cb0d916e8e396dcad98"
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
dependencies = [
update to v5.0.0
2022-08-12 19:50:08 +01:00
"kqueue-sys",
"libc",
]
[[package]]
name = "kqueue-sys"
version = "1.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8367585489f01bc55dd27404dcf56b95e6da061a256a666ab23be9ba96a2e587"
dependencies = [
Upgrade to bitflags 2.0 This version of bitflags now requires us to explicitly list the traits that we want to derive for our bit-flags structs.
2023-03-13 12:47:14 +00:00
"bitflags 1.3.2",
update to v5.0.0
2022-08-12 19:50:08 +01:00
"libc",
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "kv-log-macro"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0de8b303297635ad57c9f5059fd9cee7a47f8e8daa09df0fcd07dd39fb22977f"
dependencies = [
"log",
]
[[package]]
name = "lazy_static"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
dependencies = [
"spin",
]
[[package]]
name = "libc"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.2.147"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "b4668fb0ea861c1df094127ac5f1da3409a82116a4ba74fca2e58ef927159bb3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "libm"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.2.7"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "f7012b1bbb0719e1097c47611d3898568c546d597c2e74d66f6087edd5233ff4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "libsqlite3-sys"
Upgrade dependency to latest rusqlite.
2023-03-30 13:33:44 +01:00
version = "0.26.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependency to latest rusqlite.
2023-03-30 13:33:44 +01:00
checksum = "afc22eff61b133b115c6e8c74e818c628d6d5e7a502afea6f64dee076dd94326"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
fix segfault on static bin see https://github.com/rusqlite/rusqlite/issues/914 sha256: 684ebc4b8c270fc63beba185f6c54ceeb98734f13aa7aeca9b64acb33432a21c
2021-08-25 19:37:58 +01:00
"cc",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"pkg-config",
"vcpkg",
]
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
[[package]]
name = "linux-raw-sys"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.3.8"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "ef53942eb7bf7ff43a617b3e2c1c4a5ecf5944a7c1bc12d7ee39bbb15e5c1519"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
[[package]]
name = "lock_api"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.4.10"
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "c1cc9717a20b1bb222f333e6a92fd32f7d8a18ddc5a3191a11af45dcbf4dcd16"
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
dependencies = [
Update `rsa` dependency (and use `x25519-dalek` prerelease) - arti#448 and arti!607 highlight an issue with upgrading `rsa`: namely, the `x25519-dalek` version previously used has a hard dependency on `zeroize` 1.3, which creates a dependency conflict. - However, `x25519-dalek` version `2.0.0-pre.1` relaxes this dependency. Reviewing the changelogs, it doesn't look like that version is substantially different from the current one at all, so it should be safe to use despite the "prerelease" tag. - The new `x25519-dalek` version also bumps `rand_core`, which means we don't have to use the RNG compat wrapper in `tor-llcrypto` as much. closes arti#448
2022-07-05 11:57:10 +01:00
"autocfg",
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
"scopeguard",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "log"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.4.19"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "b06a4cde4c0f271a446782e3eff8de789548ce57dbc8eca9292c27f4a42004b4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"value-bag",
]
[[package]]
name = "lzma-sys"
use newer version of zstd and lzma
2022-10-29 18:31:05 +01:00
version = "0.1.20"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
use newer version of zstd and lzma
2022-10-29 18:31:05 +01:00
checksum = "5fda04ab3764e6cde78b9974eec4f779acaba7c4e84b36eca3cf77c581b85d27"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"cc",
"libc",
"pkg-config",
]
[[package]]
name = "matchers"
Upgrade to latest tracing-{subscriber,journald}
2021-10-24 03:23:26 +01:00
version = "0.1.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade to latest tracing-{subscriber,journald}
2021-10-24 03:23:26 +01:00
checksum = "8263075bb86c5a1b1427b5ae862e8889656f126e9f77c484496e8b47cf5c5558"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"regex-automata",
]
[[package]]
name = "matches"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "0.1.10"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "2532096657941c2fea9c289d370a250971c689d4f143798ff67113ec042024a5"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
[[package]]
name = "matrixmultiply"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.3.7"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "090126dc04f95dc0d1c1c91f61bdd474b3930ca064c1edc8a849da2c6cbe1e77"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
dependencies = [
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
"autocfg",
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
"rawpointer",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "memchr"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
version = "2.5.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
checksum = "2dffe52ecf27772e601905b7522cb4ef790d2cc203488bbd0e2fe85fcb74566d"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "memmap2"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.7.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "f49388d20533534cd19360ad3d6a7dadc885944aa802ba3995040c5ec11288c6"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"libc",
]
[[package]]
name = "merlin"
version = "2.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4e261cf0f8b3c42ded9f7d2bb59dea03aa52bc8a1cbc7482f9fc3fd1229d3b42"
dependencies = [
"byteorder",
"keccak",
"rand_core 0.5.1",
"zeroize",
]
Upgrade to newer version of config crate.
2022-02-25 14:17:37 +00:00
[[package]]
name = "minimal-lexical"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "68354c5c6bd36d73ff3feceb05efa59b6acb7626617f4962be322a825e61f79a"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
[[package]]
name = "miniz_oxide"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b275950c28b37e794e8c55d88aeb5e139d0ce23fdbbeda68f8d7174abdf9e8fa"
dependencies = [
"adler",
]
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
[[package]]
name = "miniz_oxide"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e7810e0be55b428ada41041c41f32c9f1a42817901b4ccf45fa3d4b6561e74c7"
dependencies = [
"adler",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "mio"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.8.8"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "927a765cd3fc26206e66b296465fa9d3e5ab003e651c1b3c060e7956d96b19d2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"libc",
"log",
Run cargo-update in preparation for Arti 0.2.0 (Doing this a few days ahead of time to give updated code time to get testing)
2022-03-29 18:22:28 +01:00
"wasi 0.11.0+wasi-snapshot-preview1",
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
"windows-sys 0.48.0",
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
]
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
[[package]]
name = "nalgebra"
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
version = "0.29.0"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
checksum = "d506eb7e08d6329505faa8a3a00a5dcc6de9f76e0c77e4b75763ae3c770831ff"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
dependencies = [
"approx",
"matrixmultiply",
"nalgebra-macros",
"num-complex",
"num-rational",
"num-traits",
"rand 0.8.5",
"rand_distr",
"simba",
"typenum",
]
[[package]]
name = "nalgebra-macros"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "01fcc0b8149b4632adc89ac3b7b31a12fb6099a0317a4eb2ebff574ef7de7218"
dependencies = [
"proc-macro2",
"quote",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "native-tls"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
version = "0.2.11"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
checksum = "07226173c32f2926027b63cce4bcd8076c3552846cbe7925f3aaffeac0a3b92e"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"lazy_static",
"libc",
"log",
"openssl",
"openssl-probe",
"openssl-sys",
"schannel",
"security-framework",
"security-framework-sys",
"tempfile",
]
[[package]]
name = "nix"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "0.26.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "bfdda3d196821d6af13126e40375cdf7da646a96114af134d5f417a9a1dc8e1a"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Upgrade to bitflags 2.0 This version of bitflags now requires us to explicitly list the traits that we want to derive for our bit-flags structs.
2023-03-13 12:47:14 +00:00
"bitflags 1.3.2",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"libc",
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
"static_assertions",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "nom"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "7.1.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "d273983c5a657a70a3e8f2a01329822f3b8c8172b73826411a55751e404a0a4a"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"memchr",
Upgrade to newer version of config crate.
2022-02-25 14:17:37 +00:00
"minimal-lexical",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
[[package]]
name = "notify"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "6.0.1"
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "5738a2795d57ea20abec2d6d76c6081186709c0024187cd5977265eda6598b51"
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
dependencies = [
Upgrade to bitflags 2.0 This version of bitflags now requires us to explicitly list the traits that we want to derive for our bit-flags structs.
2023-03-13 12:47:14 +00:00
"bitflags 1.3.2",
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
"filetime",
"inotify",
update to v5.0.0
2022-08-12 19:50:08 +01:00
"kqueue",
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
"libc",
update to v5.0.0
2022-08-12 19:50:08 +01:00
"mio",
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
"walkdir",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"windows-sys 0.45.0",
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
]
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
[[package]]
name = "nu-ansi-term"
version = "0.46.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "77a8165726e8236064dbb45459242600304b42a5ea24ee2948e18e023bf7ba84"
dependencies = [
"overload",
"winapi",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "num-bigint"
update dependencies
2021-11-17 19:17:08 +00:00
version = "0.4.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update dependencies
2021-11-17 19:17:08 +00:00
checksum = "f93ab6289c7b344a8a9f60f88d80aa20032336fe78da341afc91c8a2341fc75f"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Update `rsa` dependency (and use `x25519-dalek` prerelease) - arti#448 and arti!607 highlight an issue with upgrading `rsa`: namely, the `x25519-dalek` version previously used has a hard dependency on `zeroize` 1.3, which creates a dependency conflict. - However, `x25519-dalek` version `2.0.0-pre.1` relaxes this dependency. Reviewing the changelogs, it doesn't look like that version is substantially different from the current one at all, so it should be safe to use despite the "prerelease" tag. - The new `x25519-dalek` version also bumps `rand_core`, which means we don't have to use the RNG compat wrapper in `tor-llcrypto` as much. closes arti#448
2022-07-05 11:57:10 +01:00
"autocfg",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"num-integer",
"num-traits",
]
[[package]]
name = "num-bigint-dig"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.8.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "53ba502077159ace3aa56c25449a007173a406607a94ef665247246191eb38b1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"byteorder",
"lazy_static",
Back down x25519-dalek to 2.0.0-pre.1 from 2.0.0-rc.2 ========================= Notes from nickm: (This differs from pinkforest's original MR: It removes the Cargo.lock changes and the version bump on tor-llcrypto.) Minimal Cargo.lock changes from downgrade. (These are exactly those changes generated by running "build" and "test".) There are several reasons to do this: * It's best to bump all of our dalek dependencies at once to rc.3 or later, rather than the piecemeal approach we've been stuck with so far. * We don't want to do this bump right now, since there are some tricky questions about clamping we need to figure out (see #808), and we need to make sure we get them right, and we're in a distracted this week. * We _do_ need to move away from 2.0.0-rc.2 right now, since it was causing a failure in `cargo install arti`, and then it got yanked. Thanks to pinkforest for helping us out here and explaining all of this! Fixes #926. Commit-edited-by: Nick Mathewson <nickm@torproject.org>
2023-06-27 01:45:36 +01:00
"libm",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"num-integer",
"num-iter",
"num-traits",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"smallvec",
"zeroize",
]
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
[[package]]
name = "num-complex"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "0.4.3"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "02e0d21255c828d6f128a1e41534206671e8c3ea0c62f32291e808dc82cff17d"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
dependencies = [
"num-traits",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "num-integer"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
version = "0.1.45"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
checksum = "225d3389fb3509a24c93f5c29eb6bde2586b98d9f016636dff58d7c6f7569cd9"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Update `rsa` dependency (and use `x25519-dalek` prerelease) - arti#448 and arti!607 highlight an issue with upgrading `rsa`: namely, the `x25519-dalek` version previously used has a hard dependency on `zeroize` 1.3, which creates a dependency conflict. - However, `x25519-dalek` version `2.0.0-pre.1` relaxes this dependency. Reviewing the changelogs, it doesn't look like that version is substantially different from the current one at all, so it should be safe to use despite the "prerelease" tag. - The new `x25519-dalek` version also bumps `rand_core`, which means we don't have to use the RNG compat wrapper in `tor-llcrypto` as much. closes arti#448
2022-07-05 11:57:10 +01:00
"autocfg",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"num-traits",
]
[[package]]
name = "num-iter"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
version = "0.1.43"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
checksum = "7d03e6c028c5dc5cac6e2dec0efda81fc887605bb3d884578bb6d6bf7514e252"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Update `rsa` dependency (and use `x25519-dalek` prerelease) - arti#448 and arti!607 highlight an issue with upgrading `rsa`: namely, the `x25519-dalek` version previously used has a hard dependency on `zeroize` 1.3, which creates a dependency conflict. - However, `x25519-dalek` version `2.0.0-pre.1` relaxes this dependency. Reviewing the changelogs, it doesn't look like that version is substantially different from the current one at all, so it should be safe to use despite the "prerelease" tag. - The new `x25519-dalek` version also bumps `rand_core`, which means we don't have to use the RNG compat wrapper in `tor-llcrypto` as much. closes arti#448
2022-07-05 11:57:10 +01:00
"autocfg",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"num-integer",
"num-traits",
]
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
[[package]]
name = "num-rational"
Run cargo upgrade in preparation for release.
2022-06-24 12:55:26 +01:00
version = "0.4.1"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo upgrade in preparation for release.
2022-06-24 12:55:26 +01:00
checksum = "0638a1c9d0a3c0914158145bc76cff373a75a627e6ecbfb71cbe6f453a5a19b0"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
dependencies = [
Update `rsa` dependency (and use `x25519-dalek` prerelease) - arti#448 and arti!607 highlight an issue with upgrading `rsa`: namely, the `x25519-dalek` version previously used has a hard dependency on `zeroize` 1.3, which creates a dependency conflict. - However, `x25519-dalek` version `2.0.0-pre.1` relaxes this dependency. Reviewing the changelogs, it doesn't look like that version is substantially different from the current one at all, so it should be safe to use despite the "prerelease" tag. - The new `x25519-dalek` version also bumps `rand_core`, which means we don't have to use the RNG compat wrapper in `tor-llcrypto` as much. closes arti#448
2022-07-05 11:57:10 +01:00
"autocfg",
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
"num-integer",
"num-traits",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "num-traits"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
version = "0.2.15"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
checksum = "578ede34cf02f8924ab9447f50c28075b4d3e5b269972345e7e0372b38c6cdcd"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Update `rsa` dependency (and use `x25519-dalek` prerelease) - arti#448 and arti!607 highlight an issue with upgrading `rsa`: namely, the `x25519-dalek` version previously used has a hard dependency on `zeroize` 1.3, which creates a dependency conflict. - However, `x25519-dalek` version `2.0.0-pre.1` relaxes this dependency. Reviewing the changelogs, it doesn't look like that version is substantially different from the current one at all, so it should be safe to use despite the "prerelease" tag. - The new `x25519-dalek` version also bumps `rand_core`, which means we don't have to use the RNG compat wrapper in `tor-llcrypto` as much. closes arti#448
2022-07-05 11:57:10 +01:00
"autocfg",
Back down x25519-dalek to 2.0.0-pre.1 from 2.0.0-rc.2 ========================= Notes from nickm: (This differs from pinkforest's original MR: It removes the Cargo.lock changes and the version bump on tor-llcrypto.) Minimal Cargo.lock changes from downgrade. (These are exactly those changes generated by running "build" and "test".) There are several reasons to do this: * It's best to bump all of our dalek dependencies at once to rc.3 or later, rather than the piecemeal approach we've been stuck with so far. * We don't want to do this bump right now, since there are some tricky questions about clamping we need to figure out (see #808), and we need to make sure we get them right, and we're in a distracted this week. * We _do_ need to move away from 2.0.0-rc.2 right now, since it was causing a failure in `cargo install arti`, and then it got yanked. Thanks to pinkforest for helping us out here and explaining all of this! Fixes #926. Commit-edited-by: Nick Mathewson <nickm@torproject.org>
2023-06-27 01:45:36 +01:00
"libm",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "num_cpus"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "1.15.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "0fac9e2da13b5eb447a6ce3d392f23a29d8694bff781bf03a16cd9ac8697593b"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
"hermit-abi 0.2.6",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"libc",
]
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
[[package]]
name = "num_enum"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
version = "0.6.1"
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
checksum = "7a015b430d3c108a207fd776d2e2196aaf8b1cf8cf93253e3a097ff3085076a1"
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
dependencies = [
"num_enum_derive",
]
[[package]]
name = "num_enum_derive"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
version = "0.6.1"
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
checksum = "96667db765a921f7b295ffee8b60472b686a51d4f21c2ee4ffdb94c7013b65a6"
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
dependencies = [
"proc-macro-crate",
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
]
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
[[package]]
name = "object"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.30.4"
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "03b4680b86d9cfafba8fc491dc9b6df26b68cf40e9e6cd73909194759a63c385"
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
dependencies = [
"memchr",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "once_cell"
tor-geoip: Add new crate with GeoIP database functionality - This adds a new crate, `tor-geoip`, which can parse and perform lookups in the GeoIP database C-tor already uses (generated by a maintenance utility in the C-tor codebase). - We embed a copy of C-tor's databases with the crate and use `include_str!` to ship them with the binary, bloating its size somewhat. - This does, however, solve the problem of figuring out how to distribute these. - The plan is to gate this functionality behind a feature flag anyway, so the cost should be nil unless explicitly opted into. Part of tpo/core/onionmasq#47.
2023-06-13 15:27:14 +01:00
version = "1.18.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
tor-geoip: Add new crate with GeoIP database functionality - This adds a new crate, `tor-geoip`, which can parse and perform lookups in the GeoIP database C-tor already uses (generated by a maintenance utility in the C-tor codebase). - We embed a copy of C-tor's databases with the crate and use `include_str!` to ship them with the binary, bloating its size somewhat. - This does, however, solve the problem of figuring out how to distribute these. - The plan is to gate this functionality behind a feature flag anyway, so the cost should be nil unless explicitly opted into. Part of tpo/core/onionmasq#47.
2023-06-13 15:27:14 +01:00
checksum = "dd8b5dd2ae5ed71462c540258bedcb51965123ad7e7ccf4b9a8cafaa4a63576d"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "opaque-debug"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "624a8340c38c1b80fd549087862da4ba43e08858af025b236e509b6649fc13d5"
[[package]]
name = "openssl"
Bump openssl because RUSTSEC-2023-0044
2023-06-21 11:57:34 +01:00
version = "0.10.55"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump openssl because RUSTSEC-2023-0044
2023-06-21 11:57:34 +01:00
checksum = "345df152bc43501c5eb9e4654ff05f794effb78d4efe3d53abc158baddc0703d"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Upgrade to bitflags 2.0 This version of bitflags now requires us to explicitly list the traits that we want to derive for our bit-flags structs.
2023-03-13 12:47:14 +00:00
"bitflags 1.3.2",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"foreign-types",
"libc",
"once_cell",
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
"openssl-macros",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"openssl-sys",
]
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
[[package]]
name = "openssl-macros"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "0.1.1"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "a948666b637a0f465e8564c73e89d4dde00d72d4d473cc972f390fc3dcee7d9c"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "openssl-probe"
Run "cargo update" in preparation for monday's release.
2022-01-28 13:38:54 +00:00
version = "0.1.5"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for monday's release.
2022-01-28 13:38:54 +00:00
checksum = "ff011a302c396a5197692431fc1948019154afc178baf7d8e37367442a4601cf"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "openssl-src"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "111.26.0+1.1.1u"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "efc62c9f12b22b8f5208c23a7200a442b2e5999f8bdf80233852122b5a4f6f37"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"cc",
]
[[package]]
name = "openssl-sys"
Bump openssl because RUSTSEC-2023-0044
2023-06-21 11:57:34 +01:00
version = "0.9.90"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump openssl because RUSTSEC-2023-0044
2023-06-21 11:57:34 +01:00
checksum = "374533b0e45f3a7ced10fcaeccca020e66656bc03dac384f852e4e5a7a8104a6"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"cc",
"libc",
"openssl-src",
"pkg-config",
"vcpkg",
]
Run "cargo update".
2023-05-22 12:47:20 +01:00
[[package]]
name = "option-ext"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "04744f49eae99ab78e0d5c0b603ab218f515ea8cfe5a456d7629ad883a3b6e7d"
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
[[package]]
name = "os_str_bytes"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "6.5.1"
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "4d5d9eb14b174ee9aa2ef96dc2b94637a2d4b6e7cb873c7e171f0c20c6cf3eac"
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
[[package]]
name = "overload"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b15813163c1d831bf4a13c3610c05c0d03b39feb07f7e09fa234dac9b15aaf39"
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "p256"
version = "0.11.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "51f44edd08f51e2ade572f141051021c5af22677e42b7dd28a88155151c33594"
dependencies = [
"ecdsa",
"elliptic-curve",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"sha2 0.10.7",
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
]
[[package]]
name = "p384"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dfc8c5bf642dde52bb9e87c0ecd8ca5a76faac2eeed98dedb7c717997e1080aa"
dependencies = [
"ecdsa",
"elliptic-curve",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"sha2 0.10.7",
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "parking"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "2.1.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "14f2252c834a40ed9bb5422029649578e63aa341ac401f74e719dd1afda8394e"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
[[package]]
name = "parking_lot"
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
version = "0.12.1"
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
checksum = "3742b2c103b9f06bc9fff0a37ff4912935851bee6d36f3c02bcc755bcfec228f"
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
dependencies = [
"lock_api",
Run "cargo update" in preparation for next week's release.
2022-07-27 14:27:30 +01:00
"parking_lot_core",
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
]
[[package]]
name = "parking_lot_core"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.9.8"
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "93f00c865fe7cabf650081affecd3871070f26767e7b2070a3ffae14c654b447"
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
"libc",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"redox_syscall 0.3.5",
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
"smallvec",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"windows-targets 0.48.1",
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
]
CfgPath: Test serialisation round-trip with a binary format Use MessagePack. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
2022-04-27 16:35:55 +01:00
[[package]]
name = "paste"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "1.0.12"
CfgPath: Test serialisation round-trip with a binary format Use MessagePack. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
2022-04-27 16:35:55 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "9f746c4065a8fa3fe23974dd82f15431cc8d40779821001404d10d2e79ca7d79"
CfgPath: Test serialisation round-trip with a binary format Use MessagePack. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
2022-04-27 16:35:55 +01:00
Upgrade to newer version of config crate.
2022-02-25 14:17:37 +00:00
[[package]]
name = "pathdiff"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8835116a5c179084a830efb3adc117ab007512b535bc1a21c991d3b32a6b44dd"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
[[package]]
name = "pem"
version = "0.8.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fd56cbd21fea48d0c440b41cd69c589faacade08c992d9a54e471b79d0fd13eb"
dependencies = [
Upgrade serde_with dependency to 3.0.0
2023-05-22 12:49:58 +01:00
"base64 0.13.1",
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
"once_cell",
"regex",
]
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "pem-rfc7468"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "24d159833a9105500e0398934e205e0773f0b27529557134ecfc51c27646adac"
dependencies = [
"base64ct",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "pem-rfc7468"
update rsa to 0.9.x
2023-05-08 16:24:23 +01:00
version = "0.7.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update rsa to 0.9.x
2023-05-08 16:24:23 +01:00
checksum = "88b39c9bfcfc231068454382784bb460aae594343fb030d46e9f50a645418412"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"base64ct",
]
[[package]]
name = "percent-encoding"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "2.3.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "9b2a4787296e9989611394c33f193f676704af1686e70b8f8033ab5ba9a35a94"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "phf"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.11.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "ade2d8b8f33c7333b51bcf0428d37e217e9f32192ae4772156f65063b8ce03dc"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"phf_macros",
"phf_shared",
]
[[package]]
name = "phf_generator"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.11.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "48e4cc64c2ad9ebe670cb8fd69dd50ae301650392e81c05f9bfcb2d5bdbc24b0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"phf_shared",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "phf_macros"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.11.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "3444646e286606587e49f3bcf1679b8cef1dc2c5ecc29ddacaffc305180d464b"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"phf_generator",
"phf_shared",
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "phf_shared"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.11.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "90fcb95eef784c2ac79119d1dd819e162b5da872ce6f3c3abe1e8ca1c082f72b"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"siphasher",
]
[[package]]
name = "pin-project"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "1.1.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "c95a7476719eab1e366eaf73d0260af3021184f18177925b07f54b30089ceead"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"pin-project-internal",
]
[[package]]
name = "pin-project-internal"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "1.1.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "39407670928234ebc5e6e580247dd567ad73a3578460c5990f9503df207e8f07"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "pin-project-lite"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
version = "0.2.9"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
checksum = "e0a7ae3ac2f1173085d398531c705756c94a4c56843785df85a60c1a0afac116"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "pin-utils"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "pkcs1"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "eff33bdbdfc54cc98a2eca766ebdec3e1b8fb7387523d5c9c9a2891da856f719"
dependencies = [
"der 0.6.1",
"pkcs8 0.9.0",
"spki 0.6.0",
"zeroize",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "pkcs1"
update rsa to 0.9.x
2023-05-08 16:24:23 +01:00
version = "0.7.5"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update rsa to 0.9.x
2023-05-08 16:24:23 +01:00
checksum = "c8ffb9f10fa047879315e6625af03c164b16962a5368d724ed16323b68ace47f"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
"der 0.7.6",
"pkcs8 0.10.2",
"spki 0.7.2",
]
[[package]]
name = "pkcs8"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9eca2c590a5f85da82668fa685c09ce2888b9430e83299debf1f34b65fd4a4ba"
dependencies = [
"der 0.6.1",
"spki 0.6.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "pkcs8"
update rsa to 0.9.x
2023-05-08 16:24:23 +01:00
version = "0.10.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update rsa to 0.9.x
2023-05-08 16:24:23 +01:00
checksum = "f950b2377845cebe5cf8b5165cb3cc1a5e0fa5cfa3e1f7f55707d8fd82e0a7b7"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
"der 0.7.6",
"spki 0.7.2",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "pkg-config"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.3.27"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "26072860ba924cbfa98ea39c8c19b4dd6a4a25423dbdf219c1eca91aa0cf6964"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "polling"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
version = "2.8.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
checksum = "4b2d323e8ca7996b3e23126511a523f7e62924d93ecd5ae73b333815b0eb3dce"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run cargo update in preparation for release.
2022-08-30 16:22:51 +01:00
"autocfg",
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
"bitflags 1.3.2",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
"concurrent-queue",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"libc",
"log",
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
"pin-project-lite",
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
"windows-sys 0.48.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "postage"
Upgrade to Postage 0.5.0
2022-04-25 21:06:31 +01:00
version = "0.5.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade to Postage 0.5.0
2022-04-25 21:06:31 +01:00
checksum = "af3fb618632874fb76937c2361a7f22afd393c982a2165595407edc75b06d3c1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"atomic",
"crossbeam-queue",
"futures",
Run "cargo update" in preparation for next week's release.
2022-07-27 14:27:30 +01:00
"parking_lot",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"pin-project",
"static_assertions",
"thiserror",
]
[[package]]
name = "ppv-lite86"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
version = "0.2.17"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for next release
2022-11-29 13:13:56 +00:00
checksum = "5b40af805b3121feab8a3c29f04d8ad262fa8e0561883e7653e024ae4479e6de"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
[[package]]
name = "proc-macro-crate"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
version = "1.3.1"
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
checksum = "7f4c021e1093a56626774e81216a4ce732a735e5bad4868a03f3ed65ca0c3919"
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
dependencies = [
"once_cell",
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
"toml_edit",
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "proc-macro2"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "1.0.63"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "7b368fba921b0dce7e60f5e04ec15e565b3303972b42bcfde1d0713b881959eb"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update" in preparation for the next release.
2022-05-24 20:08:01 +01:00
"unicode-ident",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
[[package]]
name = "quick-error"
version = "1.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a1d01941d82fa2ab50be1e79e6714289dd7cde78eba4c074bc5a4374f650dfe0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "quote"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "1.0.29"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "573015e8ab27661678357f27dc26460738fd2b6c86e46f386fde94cb5d913105"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"proc-macro2",
]
[[package]]
name = "rand"
version = "0.7.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6a6b1679d49b24bbfe0c803429aa1874472f50d9b363131f0e89fc356b544d03"
dependencies = [
"getrandom 0.1.16",
"libc",
"rand_chacha 0.2.2",
"rand_core 0.5.1",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand_hc",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "rand"
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
version = "0.8.5"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
checksum = "34af8d1a0e25924bc5b7c43c079c942339d8f0a8b57c39049bef581b46327404"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"libc",
"rand_chacha 0.3.1",
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
"rand_core 0.6.4",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "rand_chacha"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f4c8ed856279c9737206bf725bf36935d8666ead7aa69b52be55af369d193402"
dependencies = [
"ppv-lite86",
"rand_core 0.5.1",
]
[[package]]
name = "rand_chacha"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e6c10a63a0fa32252be49d21e7709d4d4baf8d231c2dbce1eaa8141b9b127d88"
dependencies = [
"ppv-lite86",
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
"rand_core 0.6.4",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "rand_core"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "90bde5296fc891b0cef12a6d03ddccc162ce7b2aff54160af9338f8d40df6d19"
dependencies = [
"getrandom 0.1.16",
]
[[package]]
name = "rand_core"
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
version = "0.6.4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
checksum = "ec0be4795e2f6a28069bec0b5ff3e2ac9bafc99e6a9a7dc3547996c5c816922c"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"getrandom 0.2.10",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
[[package]]
name = "rand_distr"
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
version = "0.4.3"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
checksum = "32cb0b9bc82b0a0876c2dd994a7e7a2683d3e7390ca40e6886785ef0c7e3ee31"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
dependencies = [
"num-traits",
"rand 0.8.5",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "rand_hc"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
dependencies = [
"rand_core 0.5.1",
]
tor-geoip: Add new crate with GeoIP database functionality - This adds a new crate, `tor-geoip`, which can parse and perform lookups in the GeoIP database C-tor already uses (generated by a maintenance utility in the C-tor codebase). - We embed a copy of C-tor's databases with the crate and use `include_str!` to ship them with the binary, bloating its size somewhat. - This does, however, solve the problem of figuring out how to distribute these. - The plan is to gate this functionality behind a feature flag anyway, so the cost should be nil unless explicitly opted into. Part of tpo/core/onionmasq#47.
2023-06-13 15:27:14 +01:00
[[package]]
name = "rangemap"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8b9283c6b06096b47afc7109834fdedab891175bb5241ee5d4f7d2546549f263"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
[[package]]
name = "rawpointer"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "60a357793950651c4ed0f3f52338f53b2f809f32d83a07f72909fa13e4c6c1e3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "redox_syscall"
Run "cargo update" in preparation for next week's release.
2022-07-27 14:27:30 +01:00
version = "0.2.16"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for next week's release.
2022-07-27 14:27:30 +01:00
checksum = "fb5a58c1855b4b6819d59012155603f0b22ad30cad752600aadfcb695265519a"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Upgrade to bitflags 2.0 This version of bitflags now requires us to explicitly list the traits that we want to derive for our bit-flags structs.
2023-03-13 12:47:14 +00:00
"bitflags 1.3.2",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
[[package]]
name = "redox_syscall"
version = "0.3.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "567664f262709473930a4bf9e51bf2ebf3348f2e748ccc50dea20646858f8f29"
dependencies = [
"bitflags 1.3.2",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "redox_users"
Final "cargo update" before 0.2.0
2022-04-01 13:05:38 +01:00
version = "0.4.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Final "cargo update" before 0.2.0
2022-04-01 13:05:38 +01:00
checksum = "b033d837a7cf162d7993aded9304e30a83213c648b6e389db233191f891e5c2b"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"getrandom 0.2.10",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"redox_syscall 0.2.16",
Run cargo-update in preparation for Arti 0.2.0 (Doing this a few days ahead of time to give updated code time to get testing)
2022-03-29 18:22:28 +01:00
"thiserror",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "regex"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "1.8.4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "d0ab3ca65655bb1e41f2a8c8cd662eb4fb035e67c3f78da1d61dffe89d07300f"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
"aho-corasick",
"memchr",
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
"regex-syntax 0.7.2",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "regex-automata"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6c230d73fb8d8c1b9c0b3135c5142a8acee3a0558fb8db5cf1cb65f8d7862132"
dependencies = [
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
"regex-syntax 0.6.29",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "regex-syntax"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.6.29"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "f162c6dd7b008981e4d40210aca20b4bd0f9b60ca9271061b07f78537722f2e1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
[[package]]
name = "regex-syntax"
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
version = "0.7.2"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
checksum = "436b050e76ed2903236f032a59761c1eb99e1b0aead2c257922771dab1fc8c78"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
[[package]]
name = "retain_mut"
Run "cargo update" in preparation for the next release.
2022-05-24 20:08:01 +01:00
version = "0.1.9"
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for the next release.
2022-05-24 20:08:01 +01:00
checksum = "4389f1d5789befaf6029ebd9f7dac4af7f7e3d61b69d4f30e2ac02b57e7712b0"
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "retry-error"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.4.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"anyhow",
]
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "rfc6979"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7743f17af12fa0b03b803ba12cd6a8d9483a587e89c69445e3909655c0b9fabb"
dependencies = [
"crypto-bigint",
"hmac",
"zeroize",
]
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
[[package]]
name = "ring"
version = "0.16.20"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3053cf52e236a3ed746dfc745aa9cacf1b791d846bdaf412f60a8d7d6e17c8fc"
dependencies = [
"cc",
"libc",
"once_cell",
"spin",
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
"untrusted 0.7.1",
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
"web-sys",
update to v5.0.0
2022-08-12 19:50:08 +01:00
"winapi",
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
]
arti: On startup, increase the NOFILE resource limit. The default soft limit is typically enough for process usage on most Unixes, but OSX has a pretty low default (256), which you can run into easily under heavy usage. With this patch, we're going to aim for as much as 16384, if we're allowed. Fixes part of #188.
2021-10-14 18:25:19 +01:00
[[package]]
name = "rlimit"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "0.9.1"
arti: On startup, increase the NOFILE resource limit. The default soft limit is typically enough for process usage on most Unixes, but OSX has a pretty low default (256), which you can run into easily under heavy usage. With this patch, we're going to aim for as much as 16384, if we're allowed. Fixes part of #188.
2021-10-14 18:25:19 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "f8a29d87a652dc4d43c586328706bb5cdff211f3f39a530f240b53f7221dab8e"
arti: On startup, increase the NOFILE resource limit. The default soft limit is typically enough for process usage on most Unixes, but OSX has a pretty low default (256), which you can run into easily under heavy usage. With this patch, we're going to aim for as much as 16384, if we're allowed. Fixes part of #188.
2021-10-14 18:25:19 +01:00
dependencies = [
"libc",
]
CfgPath: Test serialisation round-trip with a binary format Use MessagePack. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
2022-04-27 16:35:55 +01:00
[[package]]
name = "rmp"
version = "0.8.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "44519172358fd6d58656c86ab8e7fbc9e1490c3e8f14d35ed78ca0dd07403c9f"
dependencies = [
"byteorder",
"num-traits",
"paste",
]
[[package]]
name = "rmp-serde"
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
version = "1.1.1"
CfgPath: Test serialisation round-trip with a binary format Use MessagePack. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
2022-04-27 16:35:55 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
checksum = "c5b13be192e0220b8afb7222aa5813cb62cc269ebb5cac346ca6487681d2913e"
CfgPath: Test serialisation round-trip with a binary format Use MessagePack. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
2022-04-27 16:35:55 +01:00
dependencies = [
"byteorder",
"rmp",
"serde",
]
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "rsa"
version = "0.7.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "094052d5470cbcef561cb848a7209968c9f12dfa6d668f4bca048ac5de51099c"
dependencies = [
"byteorder",
"digest 0.10.7",
"num-bigint-dig",
"num-integer",
"num-iter",
"num-traits",
"pkcs1 0.4.1",
"pkcs8 0.9.0",
"rand_core 0.6.4",
"signature 1.6.4",
"smallvec",
"subtle",
"zeroize",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "rsa"
update rsa to 0.9.x
2023-05-08 16:24:23 +01:00
version = "0.9.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update rsa to 0.9.x
2023-05-08 16:24:23 +01:00
checksum = "6ab43bb47d23c1a631b4b680199a45255dce26fa9ab2fa902581f624ff13e6a8"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"byteorder",
update rsa to 0.9.x
2023-05-08 16:24:23 +01:00
"const-oid",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"num-bigint-dig",
"num-integer",
"num-iter",
"num-traits",
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
"pkcs1 0.7.5",
"pkcs8 0.10.2",
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
"rand_core 0.6.4",
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
"signature 2.1.0",
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
"spki 0.7.2",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"subtle",
"zeroize",
]
[[package]]
name = "rusqlite"
Upgrade dependency to latest rusqlite.
2023-03-30 13:33:44 +01:00
version = "0.29.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependency to latest rusqlite.
2023-03-30 13:33:44 +01:00
checksum = "549b9d036d571d42e6e85d1c1425e2ac83491075078ca9a15be021c56b1641f2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"bitflags 2.3.3",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"fallible-iterator",
"fallible-streaming-iterator",
"hashlink",
"libsqlite3-sys",
"smallvec",
Migrate tor-dirmgr from chrono to time 0.3 (This appears to be the emerging consensus of how to handle RUSTSEC-2020-0159.)
2021-10-24 15:50:21 +01:00
"time",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
[[package]]
name = "rustc-demangle"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
version = "0.1.23"
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
checksum = "d626bb9dae77e28219937af045c257c28bfd3f69333c512553507f5f9798cb76"
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "rustc_version"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bfa0f585226d2e68097d4f95d113b15b83a82e819ab25717ec0590d9584ef366"
dependencies = [
Run "cargo update" to get latest versions. Also fix a couple of warnings introduced by now-unneeded imports with new ed25519 crate. This is part of the process for releasing our next version.
2021-11-29 19:45:50 +00:00
"semver",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
[[package]]
name = "rustix"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.37.20"
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "b96e891d04aa506a6d1f318d2771bcb1c7dfda84e126660ace067c9b474bb2c0"
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
dependencies = [
"bitflags 1.3.2",
"errno",
"io-lifetimes",
"itoa",
"libc",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"linux-raw-sys",
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
"once_cell",
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
"windows-sys 0.48.0",
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
]
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
[[package]]
name = "rustls"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.21.2"
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "e32ca28af694bc1bbf399c33a516dbdf1c90090b8ab23c2bc24f834aa2247f5f"
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
dependencies = [
"log",
"ring",
update rustls to 0.21
2023-05-08 17:01:00 +01:00
"rustls-webpki",
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
"sct",
update rustls to 0.21
2023-05-08 17:01:00 +01:00
]
[[package]]
name = "rustls-webpki"
version = "0.100.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d6207cd5ed3d8dca7816f8f3725513a34609c0c765bf652b8c3cb4cfd87db46b"
dependencies = [
"ring",
"untrusted 0.7.1",
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
]
RetryTime: use strum::EnumDiscriminants to simplify loose_cmp. Also add tests for RetryTime comparison functions to make sure they work as expected.
2022-04-04 15:58:40 +01:00
[[package]]
name = "rustversion"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "1.0.12"
RetryTime: use strum::EnumDiscriminants to simplify loose_cmp. Also add tests for RetryTime comparison functions to make sure they work as expected.
2022-04-04 15:58:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "4f3208ce4d8448b3f3e7d168a73f5e0c43a61e32930de3bceeccedb388b6bf06"
RetryTime: use strum::EnumDiscriminants to simplify loose_cmp. Also add tests for RetryTime comparison functions to make sure they work as expected.
2022-04-04 15:58:40 +01:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "ryu"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "1.0.13"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "f91339c0467de62360649f8d3e185ca8de4224ff281f66000de5eb2a77a79041"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
[[package]]
name = "safe_arch"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.7.0"
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "62a7484307bd40f8f7ccbacccac730108f2cae119a3b11c74485b48aa9ea650f"
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
dependencies = [
"bytemuck",
]
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
[[package]]
name = "safelog"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.3.2"
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
dependencies = [
safelog: Make MaybeRedacted<T> opaque.
2022-11-27 19:54:30 +00:00
"derive_more",
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
"educe",
safelog: Make MaybeRedacted<T> opaque.
2022-11-27 19:54:30 +00:00
"either",
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
"fluid-let",
"serde",
"serial_test",
"static_assertions",
"thiserror",
]
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
[[package]]
name = "same-file"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "93fc1dc3aaa9bfed95e02e6eadabb4baf7e3078b0bd1b4d7b6b0b68378900502"
dependencies = [
"winapi-util",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "sanitize-filename"
Update to newer sanitize-filename and tinystr.
2022-05-23 21:02:50 +01:00
version = "0.4.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to newer sanitize-filename and tinystr.
2022-05-23 21:02:50 +01:00
checksum = "08c502bdb638f1396509467cb0580ef3b29aa2a45c5d43e5d84928241280296c"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"lazy_static",
"regex",
]
[[package]]
name = "schannel"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "0.1.21"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "713cfb06c7059f3588fb8044c0fad1d09e3c01d225e25b9220dbfdcf16dbb1b3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
"windows-sys 0.42.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
[[package]]
name = "scopeguard"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d29ab0c6d3fc0ee92fe66e2d99f700eab17a8d57d1c1d3b748380fb20baa78cd"
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
[[package]]
name = "sct"
upgrade rustls to 0.20, ignoring all deprecation warnings
2022-10-31 19:06:13 +00:00
version = "0.7.0"
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade rustls to 0.20, ignoring all deprecation warnings
2022-10-31 19:06:13 +00:00
checksum = "d53dcdb7c9f8158937a7981b48accfd39a43af418591a5d008c7b22b5e1b7ca4"
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
dependencies = [
"ring",
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
"untrusted 0.7.1",
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
]
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "sec1"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3be24c1842290c45df0a7bf069e0c268a747ad05a192f2fd7dcfdbc1cba40928"
dependencies = [
"base16ct",
"der 0.6.1",
"generic-array",
"pkcs8 0.9.0",
"subtle",
"zeroize",
]
arti: Add support for process hardening This is a compile-time feature with an associated configuration flag, both enabled by default. When it's turned on, hardening prevents the arti process from dumping core or being attached to by low-privileged processes. (This is a defense-in-depth measure, not an absolute way to prevent attacks. For more information, see [`secmem_proc`](https://docs.rs/secmem-proc/0.1.1/secmem_proc/).) Closes #364.
2022-08-08 17:28:52 +01:00
[[package]]
name = "secmem-proc"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.3.1"
arti: Add support for process hardening This is a compile-time feature with an associated configuration flag, both enabled by default. When it's turned on, hardening prevents the arti process from dumping core or being attached to by low-privileged processes. (This is a defense-in-depth measure, not an absolute way to prevent attacks. For more information, see [`secmem_proc`](https://docs.rs/secmem-proc/0.1.1/secmem_proc/).) Closes #364.
2022-08-08 17:28:52 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "d7e12533a4a14123e586ddc3e5acb70f0b0ed722f455855eec263c066f9101f8"
arti: Add support for process hardening This is a compile-time feature with an associated configuration flag, both enabled by default. When it's turned on, hardening prevents the arti process from dumping core or being attached to by low-privileged processes. (This is a defense-in-depth measure, not an absolute way to prevent attacks. For more information, see [`secmem_proc`](https://docs.rs/secmem-proc/0.1.1/secmem_proc/).) Closes #364.
2022-08-08 17:28:52 +01:00
dependencies = [
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
"anyhow",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
arti: Add support for process hardening This is a compile-time feature with an associated configuration flag, both enabled by default. When it's turned on, hardening prevents the arti process from dumping core or being attached to by low-privileged processes. (This is a defense-in-depth measure, not an absolute way to prevent attacks. For more information, see [`secmem_proc`](https://docs.rs/secmem-proc/0.1.1/secmem_proc/).) Closes #364.
2022-08-08 17:28:52 +01:00
"libc",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"rustix",
arti: Add support for process hardening This is a compile-time feature with an associated configuration flag, both enabled by default. When it's turned on, hardening prevents the arti process from dumping core or being attached to by low-privileged processes. (This is a defense-in-depth measure, not an absolute way to prevent attacks. For more information, see [`secmem_proc`](https://docs.rs/secmem-proc/0.1.1/secmem_proc/).) Closes #364.
2022-08-08 17:28:52 +01:00
"thiserror",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"windows",
arti: Add support for process hardening This is a compile-time feature with an associated configuration flag, both enabled by default. When it's turned on, hardening prevents the arti process from dumping core or being attached to by low-privileged processes. (This is a defense-in-depth measure, not an absolute way to prevent attacks. For more information, see [`secmem_proc`](https://docs.rs/secmem-proc/0.1.1/secmem_proc/).) Closes #364.
2022-08-08 17:28:52 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "security-framework"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "2.9.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "1fc758eb7bffce5b308734e9b0c1468893cae9ff70ebf13e7090be8dcbcc83a8"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Upgrade to bitflags 2.0 This version of bitflags now requires us to explicitly list the traits that we want to derive for our bit-flags structs.
2023-03-13 12:47:14 +00:00
"bitflags 1.3.2",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"core-foundation",
"core-foundation-sys",
"libc",
"security-framework-sys",
]
[[package]]
name = "security-framework-sys"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "2.9.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "f51d0c0d83bec45f16480d0ce0058397a69e48fcdc52d1dc8855fb68acbd31a7"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"core-foundation-sys",
"libc",
]
[[package]]
name = "semver"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "1.0.17"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "bebd363326d05ec3e2f532ab7660680f3b02130d780c299bca73469d521bc0ed"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "serde"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "1.0.164"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "9e8c8cf938e98f769bc164923b06dce91cea1751522f46f8466461af04c9027d"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"serde_derive",
]
[[package]]
name = "serde_derive"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "1.0.164"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "d9735b638ccc51c28bf6914d90a2e9725b377144fc612c49a611fddd1b631d68"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
tor-config: Support functions for tracking ignored config keys This turns out to need quite a complicated algorithm.
2022-05-24 19:35:00 +01:00
[[package]]
name = "serde_ignored"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "0.1.7"
tor-config: Support functions for tracking ignored config keys This turns out to need quite a complicated algorithm.
2022-05-24 19:35:00 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "94eb4a4087ba8bdf14a9208ac44fddbf55c01a6195f7edfc511ddaff6cae45a6"
tor-config: Support functions for tracking ignored config keys This turns out to need quite a complicated algorithm.
2022-05-24 19:35:00 +01:00
dependencies = [
"serde",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "serde_json"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "1.0.99"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "46266871c240a00b8f503b877622fe33430b3c7d963bdc0f2adc511e54a1eae3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"itoa",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"ryu",
"serde",
]
rpcbase: Use correct error codes, and add tests. Well, mostly correct. Our current serde implementation doesn't tell us much about what went wrong with the object, so we can't tell why we couldn't convert it into a Request. Also, our output for the data field is not as the spec says: we should bring them into conformance. Part of #825.
2023-04-12 18:32:15 +01:00
[[package]]
name = "serde_repr"
version = "0.1.12"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bcec881020c684085e55a25f7fd888954d56609ef363479dc5a1305eb0d40cab"
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
rpcbase: Use correct error codes, and add tests. Well, mostly correct. Our current serde implementation doesn't tell us much about what went wrong with the object, so we can't tell why we couldn't convert it into a Request. Also, our output for the data field is not as the spec says: we should bring them into conformance. Part of #825.
2023-04-12 18:32:15 +01:00
]
Upgrade toml to version 0.6. This required rewriting some of our error handling code in command-line processing, since the toml crate now displays and reports errors differently. (Admittedly, this code still is kind of ugly, but at least it is nicely hidden.)
2023-01-25 21:29:53 +00:00
[[package]]
name = "serde_spanned"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.6.3"
Upgrade toml to version 0.6. This required rewriting some of our error handling code in command-line processing, since the toml crate now displays and reports errors differently. (Admittedly, this code still is kind of ugly, but at least it is nicely hidden.)
2023-01-25 21:29:53 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "96426c9936fd7a0124915f9185ea1d20aa9445cc9821142f0a73bc9207a2e186"
Upgrade toml to version 0.6. This required rewriting some of our error handling code in command-line processing, since the toml crate now displays and reports errors differently. (Admittedly, this code still is kind of ugly, but at least it is nicely hidden.)
2023-01-25 21:29:53 +00:00
dependencies = [
"serde",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "serde_test"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "1.0.164"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "797c38160e2546a56e1e3439496439597e938669673ffd8af02a12f070da648f"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"serde",
]
NetDoc: Make AddrPortPattern implement serde traits I'm using serde_with here to just re-use the Display and FromStr implementations, since those are what has proven easier to type in the past.
2022-06-09 21:52:52 +01:00
[[package]]
name = "serde_with"
Upgrade serde_with dependency to 3.0.0
2023-05-22 12:49:58 +01:00
version = "3.0.0"
NetDoc: Make AddrPortPattern implement serde traits I'm using serde_with here to just re-use the Display and FromStr implementations, since those are what has proven easier to type in the past.
2022-06-09 21:52:52 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade serde_with dependency to 3.0.0
2023-05-22 12:49:58 +01:00
checksum = "9f02d8aa6e3c385bf084924f660ce2a3a6bd333ba55b35e8590b321f35d88513"
NetDoc: Make AddrPortPattern implement serde traits I'm using serde_with here to just re-use the Display and FromStr implementations, since those are what has proven easier to type in the past.
2022-06-09 21:52:52 +01:00
dependencies = [
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
"base64 0.21.2",
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
"chrono",
"hex",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"indexmap 1.9.3",
NetDoc: Make AddrPortPattern implement serde traits I'm using serde_with here to just re-use the Display and FromStr implementations, since those are what has proven easier to type in the past.
2022-06-09 21:52:52 +01:00
"serde",
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
"serde_json",
NetDoc: Make AddrPortPattern implement serde traits I'm using serde_with here to just re-use the Display and FromStr implementations, since those are what has proven easier to type in the past.
2022-06-09 21:52:52 +01:00
"serde_with_macros",
Upgrade to serde_with 2, phf 0.11. Closes #526.
2022-11-07 19:29:57 +00:00
"time",
NetDoc: Make AddrPortPattern implement serde traits I'm using serde_with here to just re-use the Display and FromStr implementations, since those are what has proven easier to type in the past.
2022-06-09 21:52:52 +01:00
]
[[package]]
name = "serde_with_macros"
Upgrade serde_with dependency to 3.0.0
2023-05-22 12:49:58 +01:00
version = "3.0.0"
NetDoc: Make AddrPortPattern implement serde traits I'm using serde_with here to just re-use the Display and FromStr implementations, since those are what has proven easier to type in the past.
2022-06-09 21:52:52 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade serde_with dependency to 3.0.0
2023-05-22 12:49:58 +01:00
checksum = "edc7d5d3932fb12ce722ee5e64dd38c504efba37567f0c402f6ca728c3b8b070"
NetDoc: Make AddrPortPattern implement serde traits I'm using serde_with here to just re-use the Display and FromStr implementations, since those are what has proven easier to type in the past.
2022-06-09 21:52:52 +01:00
dependencies = [
Run "cargo update".
2023-05-22 12:47:20 +01:00
"darling 0.20.1",
NetDoc: Make AddrPortPattern implement serde traits I'm using serde_with here to just re-use the Display and FromStr implementations, since those are what has proven easier to type in the past.
2022-06-09 21:52:52 +01:00
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
NetDoc: Make AddrPortPattern implement serde traits I'm using serde_with here to just re-use the Display and FromStr implementations, since those are what has proven easier to type in the past.
2022-06-09 21:52:52 +01:00
]
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
[[package]]
name = "serial_test"
Upgrade to serial_test 2.0.0
2023-04-28 17:35:54 +01:00
version = "2.0.0"
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade to serial_test 2.0.0
2023-04-28 17:35:54 +01:00
checksum = "0e56dd856803e253c8f298af3f4d7eb0ae5e23a737252cd90bb4f3b435033b2d"
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
dependencies = [
Upgrade serial_test in preparation for release.
2022-08-30 16:19:34 +01:00
"dashmap",
Upgrade to latest phf, serde_with, serial_test.
2022-07-19 21:47:27 +01:00
"futures",
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
"lazy_static",
Upgrade serial_test dev-dependency to 0.7.0
2022-06-07 13:04:38 +01:00
"log",
Run "cargo update" in preparation for next week's release.
2022-07-27 14:27:30 +01:00
"parking_lot",
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
"serial_test_derive",
]
[[package]]
name = "serial_test_derive"
Upgrade to serial_test 2.0.0
2023-04-28 17:35:54 +01:00
version = "2.0.0"
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade to serial_test 2.0.0
2023-04-28 17:35:54 +01:00
checksum = "91d129178576168c589c9ec973feedf7d3126c01ac2bf08795109aa35b69fb8f"
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
Implement a safe-logging facility. This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
2022-04-27 15:54:39 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
Switch from sha-1 back to sha1. As near as I can tell, the rust-crypto SHA1 crate was called `sha-1` for a while because of a conflict with a different SHA1 crate. Now they apparently have the `sha1` name back and have deprecated the `sha-1` name.
2022-11-28 14:02:16 +00:00
name = "sha1"
version = "0.10.5"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch from sha-1 back to sha1. As near as I can tell, the rust-crypto SHA1 crate was called `sha-1` for a while because of a conflict with a different SHA1 crate. Now they apparently have the `sha1` name back and have deprecated the `sha-1` name.
2022-11-28 14:02:16 +00:00
checksum = "f04293dc80c3993519f2d7f6f511707ee7094fe0c6d3406feb330cdb3540eba3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"cpufeatures",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
Add a feature to tor-llcrypto to enable sha-1/asm. SHA1 is a reasonably large part of our CPU usage (sigh), and this implementation is 20-50% faster, depending on arch.
2022-06-13 15:13:13 +01:00
"sha1-asm",
]
[[package]]
name = "sha1-asm"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "563d4f7100bc3fce234e5f37bbf63dc2752558964505ba6ac3f7204bdc59eaac"
dependencies = [
"cc",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "sha2"
Run "cargo update".
2022-01-11 14:27:22 +00:00
version = "0.9.9"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2022-01-11 14:27:22 +00:00
checksum = "4d58a1e1bf39749807d89cf2d98ac2dfa0ff1cb3faa38fbb64dd88ac8013d800"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
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
"block-buffer 0.9.0",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"cpufeatures",
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.9.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"opaque-debug",
]
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
[[package]]
name = "sha2"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.10.7"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "479fb9d862239e610720565ca91403019f2f00410f1864c5aa7479b950a76ed8"
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
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
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
"cpufeatures",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
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
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "sha3"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.10.8"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "75872d278a8f37ef87fa0ddbda7802605cb18344497949862c0d4dcb291eba60"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"keccak",
]
[[package]]
name = "sharded-slab"
Update Cargo.lock in preparation for Arti 0.0.1 release.
2021-10-29 14:40:35 +01:00
version = "0.1.4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update Cargo.lock in preparation for Arti 0.0.1 release.
2021-10-29 14:40:35 +01:00
checksum = "900fba806f70c630b0a382d0d825e17a0f19fcd059a2ade1ff237bcddf446b31"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"lazy_static",
]
[[package]]
Update shellexpand, and switch to non-fork Now we have bus>1 ownership of the crate name `shellexpand`. I have made a release, and retired `shellexpand-fork`. The new shellexpand release switches to a (quite similarly) unforked version of `dirs`.
2022-08-05 15:36:47 +01:00
name = "shellexpand"
Update to shellexpand 3.1.0 so we can use dirs 5 everywhere Results of precisely cargo update -p shellexpand Incorporates changes I have made to shellexpand to allow use of dirs 4 *or* dirs 5.
2023-03-24 11:30:14 +00:00
version = "3.1.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to shellexpand 3.1.0 so we can use dirs 5 everywhere Results of precisely cargo update -p shellexpand Incorporates changes I have made to shellexpand to allow use of dirs 4 *or* dirs 5.
2023-03-24 11:30:14 +00:00
checksum = "da03fa3b94cc19e3ebfc88c4229c49d8f08cdbd1228870a45f0ffdf84988e14b"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Update to shellexpand 3.1.0 so we can use dirs 5 everywhere Results of precisely cargo update -p shellexpand Incorporates changes I have made to shellexpand to allow use of dirs 4 *or* dirs 5.
2023-03-24 11:30:14 +00:00
"dirs",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "signal-hook"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
version = "0.3.15"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
checksum = "732768f1176d21d09e076c23a93123d40bba92d50c4058da34d45c8de8e682b9"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"libc",
"signal-hook-registry",
]
Add functionality to listen for SIGHUPs.
2022-08-25 13:34:41 +01:00
[[package]]
name = "signal-hook-async-std"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0c4aa94397e2023af5b7cff5b8d4785e935cfb77f0e4aab0cae3b26258ace556"
dependencies = [
"async-io",
"futures-lite",
"libc",
"signal-hook",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "signal-hook-registry"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
version = "1.4.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
checksum = "d8229b473baa5980ac72ef434c4415e70c4b5e71b423043adb4ba059f89c99a1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"libc",
]
[[package]]
name = "signature"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
version = "1.6.4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
checksum = "74233d3b3b2f6d4b006dc19dee745e73e2a6bfb6f93607cd3b02bd5b00797d7c"
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
dependencies = [
"digest 0.10.7",
"rand_core 0.6.4",
]
Upgrade to latest rsa crate.
2023-01-19 20:22:18 +00:00
[[package]]
name = "signature"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "2.1.0"
Upgrade to latest rsa crate.
2023-01-19 20:22:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "5e1788eed21689f9cf370582dfc467ef36ed9c707f073528ddafa8d83e3b8500"
Upgrade rsa to 0.7. Closes #613.
2022-10-28 18:38:42 +01:00
dependencies = [
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
Upgrade rsa to 0.7. Closes #613.
2022-10-28 18:38:42 +01:00
"rand_core 0.6.4",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
[[package]]
name = "simba"
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
version = "0.6.0"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
checksum = "f0b7840f121a46d63066ee7a99fc81dcabbc6105e437cae43528cea199b5a05f"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
dependencies = [
"approx",
"num-complex",
"num-traits",
"paste",
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
"wide",
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "simple_asn1"
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
version = "0.6.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
checksum = "adc4e5204eb1910f40f9cfa375f6f05b68c3abac4b6fd879c8ff5e7ae8a0a085"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"num-bigint",
"num-traits",
"thiserror",
Migrate tor-dirmgr from chrono to time 0.3 (This appears to be the emerging consensus of how to handle RUSTSEC-2020-0159.)
2021-10-24 15:50:21 +01:00
"time",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "siphasher"
Run cargo-update in preparation for Arti 0.2.0 (Doing this a few days ahead of time to give updated code time to get testing)
2022-03-29 18:22:28 +01:00
version = "0.3.10"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo-update in preparation for Arti 0.2.0 (Doing this a few days ahead of time to give updated code time to get testing)
2022-03-29 18:22:28 +01:00
checksum = "7bd3e3206899af3f8b12af284fafc038cc1dc2b41d1b89dd17297221c5d225de"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "slab"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
version = "0.4.8"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
checksum = "6528351c9bc8ab22353f9d776db39a20288e8d6c37ef8cfe3317cf875eecfc2d"
Run "cargo update" in preparation for next week's releases.
2022-07-20 13:37:13 +01:00
dependencies = [
"autocfg",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
hsclient: Implement connection attempt tracking state machine This compiles, but it cannot work yet. Nor can it conveniently be tested.
2023-02-24 12:21:04 +00:00
[[package]]
name = "slotmap"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e1e08e261d0e8f5c43123b7adf3e4ca1690d655377ac93a03b2c9d3e98de1342"
dependencies = [
"version_check",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "smallvec"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
version = "1.10.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
checksum = "a507befe795404456341dfab10cef66ead4c041f62b8b11bbb92bffe5d0953e0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "socket2"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.4.9"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "64a4a911eed85daf18834cfaa86a79b7d266ff93ff5ba14005426219480ed662"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"libc",
update to v5.0.0
2022-08-12 19:50:08 +01:00
"winapi",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "spin"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6e63cff320ae2c57904679ba7cb63280a3dc4613885beafb148ee7bf9aa9042d"
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "spki"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "67cf02bbac7a337dc36e4f5a693db6c21e7863f45070f7064577eb4367a3212b"
dependencies = [
"base64ct",
"der 0.6.1",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "spki"
update rsa to 0.9.x
2023-05-08 16:24:23 +01:00
version = "0.7.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update rsa to 0.9.x
2023-05-08 16:24:23 +01:00
checksum = "9d1e996ef02c474957d681f1b05213dfb0abab947b446a62d37770b23500184a"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Update `rsa` dependency (and use `x25519-dalek` prerelease) - arti#448 and arti!607 highlight an issue with upgrading `rsa`: namely, the `x25519-dalek` version previously used has a hard dependency on `zeroize` 1.3, which creates a dependency conflict. - However, `x25519-dalek` version `2.0.0-pre.1` relaxes this dependency. Reviewing the changelogs, it doesn't look like that version is substantially different from the current one at all, so it should be safe to use despite the "prerelease" tag. - The new `x25519-dalek` version also bumps `rand_core`, which means we don't have to use the RNG compat wrapper in `tor-llcrypto` as much. closes arti#448
2022-07-05 11:57:10 +01:00
"base64ct",
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
"der 0.7.6",
]
[[package]]
name = "ssh-encoding"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "19cfdc32e0199062113edf41f344fbf784b8205a94600233c84eb838f45191e1"
dependencies = [
"base64ct",
"pem-rfc7468 0.6.0",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"sha2 0.10.7",
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
]
[[package]]
name = "ssh-key"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "288d8f5562af5a3be4bda308dd374b2c807b940ac370b5efa1c99311da91d9a1"
dependencies = [
"ed25519-dalek",
"p256",
"p384",
"rand_core 0.6.4",
"rsa 0.7.2",
"sec1",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"sha2 0.10.7",
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
"signature 1.6.4",
"ssh-encoding",
"zeroize",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "static_assertions"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a2eb9349b6444b326872e140eb1cf5e7c522154d69e7a0ffb0fb81c06b37543f"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
[[package]]
name = "statrs"
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
version = "0.16.0"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
checksum = "2d08e5e1748192713cc281da8b16924fb46be7b0c2431854eadc785823e5696e"
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
dependencies = [
"approx",
"lazy_static",
"nalgebra",
"num-traits",
"rand 0.8.5",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "strsim"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "73473c0e59e6d5812c5dfe2a064a6444949f089e20eec9a2e5506596494e4623"
RetryTime: use strum::EnumDiscriminants to simplify loose_cmp. Also add tests for RetryTime comparison functions to make sure they work as expected.
2022-04-04 15:58:40 +01:00
[[package]]
name = "strum"
Upgrade to strum 0.25.
2023-06-21 14:12:36 +01:00
version = "0.25.0"
RetryTime: use strum::EnumDiscriminants to simplify loose_cmp. Also add tests for RetryTime comparison functions to make sure they work as expected.
2022-04-04 15:58:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade to strum 0.25.
2023-06-21 14:12:36 +01:00
checksum = "290d54ea6f91c969195bdbcd7442c8c2a2ba87da8bf60a7ee86a235d4bc1e125"
RetryTime: use strum::EnumDiscriminants to simplify loose_cmp. Also add tests for RetryTime comparison functions to make sure they work as expected.
2022-04-04 15:58:40 +01:00
dependencies = [
"strum_macros",
]
[[package]]
name = "strum_macros"
Upgrade to strum 0.25.
2023-06-21 14:12:36 +01:00
version = "0.25.0"
RetryTime: use strum::EnumDiscriminants to simplify loose_cmp. Also add tests for RetryTime comparison functions to make sure they work as expected.
2022-04-04 15:58:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade to strum 0.25.
2023-06-21 14:12:36 +01:00
checksum = "fe9f3bd7d2e45dcc5e265fbb88d6513e4747d8ef9444cf01a533119bce28a157"
RetryTime: use strum::EnumDiscriminants to simplify loose_cmp. Also add tests for RetryTime comparison functions to make sure they work as expected.
2022-04-04 15:58:40 +01:00
dependencies = [
"heck",
"proc-macro2",
"quote",
"rustversion",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
RetryTime: use strum::EnumDiscriminants to simplify loose_cmp. Also add tests for RetryTime comparison functions to make sure they work as expected.
2022-04-04 15:58:40 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "subtle"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "2.5.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "81cdd64d312baedb58e21336b31bc043b77e01cc99033ce76ef539f78e965ebc"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "syn"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
version = "1.0.109"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
checksum = "72b64191b275b66ffe2469e8af2c1cfe3bafa67b529ead792a6d0160888b4237"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for the next release.
2022-05-24 20:08:01 +01:00
"unicode-ident",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
[[package]]
name = "syn"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "2.0.22"
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "2efbeae7acf4eabd6bcdcbd11c92f45231ddda7539edc7806bd1a04a03b24616"
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
dependencies = [
"proc-macro2",
"quote",
"unicode-ident",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "tempfile"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "3.6.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "31c0432476357e58790aaa47a8efb0c5138f137343f3b5f23bd36a27e3b0a6d6"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"autocfg",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
Run "cargo update".
2022-01-11 14:27:22 +00:00
"fastrand",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"redox_syscall 0.3.5",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"rustix",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"windows-sys 0.48.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
[[package]]
name = "termcolor"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "1.2.0"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "be55cf8942feac5c765c2c993422806843c9a9a45d4d5c407ad6dd2ea95eb9b6"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
dependencies = [
"winapi-util",
]
[[package]]
name = "test-cert-gen"
Upgrade tls-api to latest versions in arti-hyper.
2022-06-07 13:01:39 +01:00
version = "0.9.0"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade tls-api to latest versions in arti-hyper.
2022-06-07 13:01:39 +01:00
checksum = "345f92b7cac59507cdaba298c5493f7c40e2063d31f6fc621105183344d5d50a"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
dependencies = [
Upgrade tls-api to latest versions in arti-hyper.
2022-06-07 13:01:39 +01:00
"once_cell",
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
"pem",
update tls-api to 0.8.0 and remove corresponding RUSTSEC from ignored list
2022-04-28 16:38:35 +01:00
"tempfile",
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
]
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
[[package]]
name = "textwrap"
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
version = "0.16.0"
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade to clap 3 with minimal changes This removes the last cargo audit override (for the unmaintained ansi_term). Don't mark options as required when they have default values: see <https://github.com/clap-rs/clap/pull/3793>.
2022-11-04 09:52:02 +00:00
checksum = "222a222a5bfe1bba4a77b45ec488a741b3cb8872e5e499451fd7d0129c9c7c3d"
Improve and future-proof the `arti` CLI This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file.
2021-10-27 17:40:00 +01:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "thiserror"
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
version = "1.0.40"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
checksum = "978c9a314bd8dc99be594bc3c175faaa9794be04a5a5e153caba6915336cebac"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
version = "1.0.40"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
checksum = "f9456a42c5b0d803c8cd86e73dd7cc9edd429499f37a3550d286d5e86720569f"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "thread_local"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
version = "1.1.7"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
checksum = "3fdd6f064ccff2d6567adcb3873ca630700f00b5ad3f060c25b5dcfd9a4ce152"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"once_cell",
]
Upgrade to new version of simple_asn1.
2021-10-22 20:44:37 +01:00
[[package]]
name = "time"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.3.22"
Upgrade to new version of simple_asn1.
2021-10-22 20:44:37 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "ea9e1b3cf1243ae005d9e74085d4d542f3125458f3a81af210d901dcd7411efd"
Upgrade to new version of simple_asn1.
2021-10-22 20:44:37 +01:00
dependencies = [
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"itoa",
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
"serde",
"time-core",
Upgrade to new version of simple_asn1.
2021-10-22 20:44:37 +01:00
"time-macros",
]
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
[[package]]
name = "time-core"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.1.1"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "7300fbefb4dadc1af235a9cef3737cea692a9d97e1b9cbcd4ebdae6f8868e6fb"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
Upgrade to new version of simple_asn1.
2021-10-22 20:44:37 +01:00
[[package]]
name = "time-macros"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.2.9"
Upgrade to new version of simple_asn1.
2021-10-22 20:44:37 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "372950940a5f07bf38dbe211d7283c9e6d7327df53794992d293e534c733d09b"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
dependencies = [
"time-core",
]
Upgrade to new version of simple_asn1.
2021-10-22 20:44:37 +01:00
RPC: Implement a "global identifier" for non-session-bound IDs These identifiers are actually only "global" with respect to a given `RpcMgr`, but they should not be forgeable or reusable across RpcMgr objects. We're going to use them so that we have a kind of identifier for `TorClient`s that we can expose to SOCKS.
2023-05-25 19:40:26 +01:00
[[package]]
name = "tiny-keccak"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2c9d3793400a45f954c52e73d068316d76b6f4e36977e3fcebb13a2721e80237"
dependencies = [
"crunchy",
]
netdoc: add a new type for Nicknames Relay nicknames are always between 1 and 19 characters long, and they're always ASCII: That means that storing them in a [u8;19] will always be possible, and always use less resources than storing them in a String. Fortunately, the tinystr crate already helps us with this kind of thing.
2022-03-10 21:38:23 +00:00
[[package]]
name = "tinystr"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "0.7.1"
netdoc: add a new type for Nicknames Relay nicknames are always between 1 and 19 characters long, and they're always ASCII: That means that storing them in a [u8;19] will always be possible, and always use less resources than storing them in a String. Fortunately, the tinystr crate already helps us with this kind of thing.
2022-03-10 21:38:23 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "7ac3f5b6856e931e15e07b478e98c8045239829a65f9156d4fa7e7788197a5ef"
netdoc: add a new type for Nicknames Relay nicknames are always between 1 and 19 characters long, and they're always ASCII: That means that storing them in a [u8;19] will always be possible, and always use less resources than storing them in a String. Fortunately, the tinystr crate already helps us with this kind of thing.
2022-03-10 21:38:23 +00:00
dependencies = [
"displaydoc",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "tinyvec"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
version = "1.6.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
checksum = "87cc5ceb3875bb20c2890005a4e226a4651264a5c75edb2421b52861a0a0cb50"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"tinyvec_macros",
]
[[package]]
name = "tinyvec_macros"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
version = "0.1.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
checksum = "1f3ccbac311fea05f86f61904b462b55fb3df8837a366dfc601a0161d0532f20"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
[[package]]
name = "tls-api"
Upgrade tls-api to latest versions in arti-hyper.
2022-06-07 13:01:39 +01:00
version = "0.9.0"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade tls-api to latest versions in arti-hyper.
2022-06-07 13:01:39 +01:00
checksum = "66d1b3dfb0a60da3e8a130c9f2432063d9979928a05c2b2cdcfc9fd05e4f53a3"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
dependencies = [
"anyhow",
"log",
"pem",
update tls-api to 0.8.0 and remove corresponding RUSTSEC from ignored list
2022-04-28 16:38:35 +01:00
"tempfile",
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
"thiserror",
"tokio",
"void",
upgrade rustls to 0.20, ignoring all deprecation warnings
2022-10-31 19:06:13 +00:00
"webpki",
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
]
[[package]]
name = "tls-api-native-tls"
Upgrade tls-api to latest versions in arti-hyper.
2022-06-07 13:01:39 +01:00
version = "0.9.0"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade tls-api to latest versions in arti-hyper.
2022-06-07 13:01:39 +01:00
checksum = "7b935bda2458120a5d2cea542013796fcf13937566580027f6a08f42a52206f7"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
dependencies = [
"anyhow",
"native-tls",
"thiserror",
"tls-api",
"tls-api-test",
"tokio",
]
Updated Cargo.lock
2023-01-06 17:35:32 +00:00
[[package]]
name = "tls-api-openssl"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "82155f245c99a3b652627f32abeacd4eae9e0fec996c1090df121e01379d28f3"
dependencies = [
"anyhow",
"openssl",
"openssl-sys",
"thiserror",
"tls-api",
"tls-api-test",
"tokio",
]
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
[[package]]
name = "tls-api-test"
Upgrade tls-api to latest versions in arti-hyper.
2022-06-07 13:01:39 +01:00
version = "0.9.0"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade tls-api to latest versions in arti-hyper.
2022-06-07 13:01:39 +01:00
checksum = "9df107843d725428d76bb159040fbae6d1524dcf25d5b24c56daa6b37ce9dbb5"
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
dependencies = [
"anyhow",
"env_logger",
"log",
"pem",
"test-cert-gen",
"tls-api",
"tokio",
"untrusted 0.6.2",
upgrade rustls to 0.20, ignoring all deprecation warnings
2022-10-31 19:06:13 +00:00
"webpki",
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "tokio"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "1.29.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "374442f06ee49c3a28a8fc9f01a2596fed7559c6b99b31279c3261778e77d84f"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update" in preparation for next week's releases.
2022-07-20 13:37:13 +01:00
"autocfg",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"backtrace",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"bytes",
"libc",
update to v5.0.0
2022-08-12 19:50:08 +01:00
"mio",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"num_cpus",
Run "cargo update" in preparation for next week's release.
2022-07-27 14:27:30 +01:00
"parking_lot",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"pin-project-lite",
"signal-hook-registry",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"socket2",
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
"tokio-macros",
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
"windows-sys 0.48.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
[[package]]
name = "tokio-macros"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
version = "2.1.0"
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
checksum = "630bdcf245f78637c13ec01ffae6187cca34625e8c63150d424b59e55af2675e"
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
]
Introduce an experimental benchmarking utility for Arti The new `arti-bench` crate does a simple end-to-end benchmark test embedding Arti: it generates some random data (of configurable amount, depending on command-line parameters), and then sends said data back and forth via Arti (which should be configured to use a local Chutney network). Additionally, the benchmark can also be run via a local SOCKS5 server (in order to benchmark the performance via a local Chutney node, for comparison). The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as required to make this work. This is very much a first cut; there are many things that should eventually get added, such as support for multiple connections, JSON output capabilities, running multiple tests, ...
2021-12-14 17:29:04 +00:00
[[package]]
name = "tokio-socks"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "51165dfa029d2a65969413a6cc96f354b86b464498702f174a4efa13608fd8c0"
dependencies = [
"either",
"futures-util",
"thiserror",
"tokio",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "tokio-util"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
version = "0.7.8"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
checksum = "806fe8c2c87eccc8b3267cbae29ed3ab2d0bd37fca70ab622e46aaa9375ddb7d"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"bytes",
"futures-core",
"futures-io",
"futures-sink",
"pin-project-lite",
"tokio",
]
[[package]]
name = "toml"
Upgrade toml to version 0.6. This required rewriting some of our error handling code in command-line processing, since the toml crate now displays and reports errors differently. (Admittedly, this code still is kind of ugly, but at least it is nicely hidden.)
2023-01-25 21:29:53 +00:00
version = "0.5.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f4f7f0dd8d50a853a531c426359045b1998f04219d88799810762cd4ad314234"
dependencies = [
"serde",
]
[[package]]
name = "toml"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.7.5"
Upgrade toml to version 0.6. This required rewriting some of our error handling code in command-line processing, since the toml crate now displays and reports errors differently. (Admittedly, this code still is kind of ugly, but at least it is nicely hidden.)
2023-01-25 21:29:53 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "1ebafdf5ad1220cb59e7d17cf4d2c72015297b75b19a10472f99b89225089240"
Upgrade toml to version 0.6. This required rewriting some of our error handling code in command-line processing, since the toml crate now displays and reports errors differently. (Admittedly, this code still is kind of ugly, but at least it is nicely hidden.)
2023-01-25 21:29:53 +00:00
dependencies = [
"serde",
"serde_spanned",
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
"toml_datetime",
"toml_edit",
Upgrade toml to version 0.6. This required rewriting some of our error handling code in command-line processing, since the toml crate now displays and reports errors differently. (Admittedly, this code still is kind of ugly, but at least it is nicely hidden.)
2023-01-25 21:29:53 +00:00
]
Upgrade to latest toml crate. (None of the breaking changes affect us this time.)
2023-02-14 16:05:48 +00:00
[[package]]
name = "toml_datetime"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.6.3"
Upgrade to latest toml crate. (None of the breaking changes affect us this time.)
2023-02-14 16:05:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "7cda73e2f1397b1262d6dfdcef8aafae14d1de7748d66822d3bfeeb6d03e5e4b"
Upgrade toml to version 0.6. This required rewriting some of our error handling code in command-line processing, since the toml crate now displays and reports errors differently. (Admittedly, this code still is kind of ugly, but at least it is nicely hidden.)
2023-01-25 21:29:53 +00:00
dependencies = [
"serde",
]
[[package]]
name = "toml_edit"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.19.11"
Upgrade to latest toml crate. (None of the breaking changes affect us this time.)
2023-02-14 16:05:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "266f016b7f039eec8a1a80dfe6156b633d208b9fccca5e4db1d6775b0c4e34a7"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"indexmap 2.0.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"serde",
Upgrade toml to version 0.6. This required rewriting some of our error handling code in command-line processing, since the toml crate now displays and reports errors differently. (Admittedly, this code still is kind of ugly, but at least it is nicely hidden.)
2023-01-25 21:29:53 +00:00
"serde_spanned",
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
"toml_datetime",
"winnow",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
Make a new empty tor-async-utils crate.
2023-03-29 14:02:20 +01:00
[[package]]
name = "tor-async-utils"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.1.2"
Make a new empty tor-async-utils crate.
2023-03-29 14:02:20 +01:00
dependencies = [
"futures",
Move functionality from tor_basic_utils to tor_async_utils This commit is mostly code movement; I'd recommend reviewing it with git's `--color-moved` option.
2023-03-29 14:17:13 +01:00
"futures-await-test",
Make a new empty tor-async-utils crate.
2023-03-29 14:02:20 +01:00
"pin-project",
Move functionality from tor_basic_utils to tor_async_utils This commit is mostly code movement; I'd recommend reviewing it with git's `--color-moved` option.
2023-03-29 14:17:13 +01:00
"postage",
Make a new empty tor-async-utils crate.
2023-03-29 14:02:20 +01:00
"thiserror",
Move functionality from tor_basic_utils to tor_async_utils This commit is mostly code movement; I'd recommend reviewing it with git's `--color-moved` option.
2023-03-29 14:17:13 +01:00
"tokio",
"void",
Make a new empty tor-async-utils crate.
2023-03-29 14:02:20 +01:00
]
Introduce tor-basic-utils Empty crate right now
2022-03-04 11:13:29 +00:00
[[package]]
name = "tor-basic-utils"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.7.2"
Introduce tor-basic-utils Empty crate right now
2022-03-04 11:13:29 +00:00
dependencies = [
Provide define_accessor_trait and use it to generate CircMgrConfig
2022-03-16 19:30:10 +00:00
"derive_more",
Introduce tor-basic-utils Empty crate right now
2022-03-04 11:13:29 +00:00
"educe",
New facility for deterministic and reproducible test PRNGs. The new `testing_rng()` function is meant as a replacement for thread_rng() for use in unit tests. By default, it uses a randomly seeded RNG, but prints the seed before the test so that you can reproduce any failures that occur. You can override this via the environment to use a previous seed, or by using a deterministic seed for all your tests. Backend for #486.
2022-05-31 22:43:55 +01:00
"hex",
tor-basic-utils: Provide IoErrorExt is_not_a_directory() We're going to want this functionality, which isn't in the stable stdlib.
2022-08-18 15:16:24 +01:00
"libc",
Include a HashSet variant that can be keyed on multiple keys. Every element in the set has up to N keys, each of which may have differnt types. No value for any key may correspond to more than one element in the set. These properties can be provided, via a macro, for values of N between 1 and $BIG_ENOUGH. We'll use this to implement a type that holds HasRelayIds.
2022-09-28 21:22:48 +01:00
"paste",
Move RetryDelay from dirmgr to basic-utils. This (almost) a pure code-movement commit: it also makes one public function private in order to suppress a warning.
2022-03-16 12:31:54 +00:00
"rand 0.8.5",
New facility for deterministic and reproducible test PRNGs. The new `testing_rng()` function is meant as a replacement for thread_rng() for use in unit tests. By default, it uses a randomly seeded RNG, but prints the seed before the test so that you can reproduce any failures that occur. You can override this via the environment to use a previous seed, or by using a deterministic seed for all your tests. Backend for #486.
2022-05-31 22:43:55 +01:00
"rand_chacha 0.3.1",
tor-basic-utils: Provide helper for serde flexible parsing
2022-11-17 17:21:18 +00:00
"serde",
Include a HashSet variant that can be keyed on multiple keys. Every element in the set has up to N keys, each of which may have differnt types. No value for any key may correspond to more than one element in the set. These properties can be provided, via a macro, for values of N between 1 and $BIG_ENOUGH. We'll use this to implement a type that holds HasRelayIds.
2022-09-28 21:22:48 +01:00
"slab",
New facility for deterministic and reproducible test PRNGs. The new `testing_rng()` function is meant as a replacement for thread_rng() for use in unit tests. By default, it uses a randomly seeded RNG, but prints the seed before the test so that you can reproduce any failures that occur. You can override this via the environment to use a previous seed, or by using a deterministic seed for all your tests. Backend for #486.
2022-05-31 22:43:55 +01:00
"thiserror",
Introduce tor-basic-utils Empty crate right now
2022-03-04 11:13:29 +00:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "tor-bytes"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.7.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"bytes",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
tor-bytes: Provide nested writers
2022-06-07 20:25:41 +01:00
"educe",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"generic-array",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"getrandom 0.2.10",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"hex-literal",
Upgrade to latest rsa crate.
2023-01-19 20:22:18 +00:00
"signature 1.6.4",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"thiserror",
tor-bytes: Use InternalError. This crate's Error type is too low-level to have an ErrorKind, but it does make sense to use InternalError for the internal errors here.
2022-02-09 19:39:04 +00:00
"tor-error",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-llcrypto",
New SecretBuf type in tor-bytes This Writer is a simple wrapper around `Vec<u8>` that makes sure that its contents are cleared whenever they are dropped _or reallocated_. The reallocation is the important part here: without that, we risk not zeroizing the first allocation of the buffer.
2022-08-01 19:11:51 +01:00
"zeroize",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "tor-cell"
Bump minor versions on crates with breaking changes Done with: ``` cargo set-version --bump minor -p tor-hsclient cargo set-version --bump minor -p arti-rpcserver cargo set-version --bump minor -p tor-hscrypto cargo set-version --bump minor -p tor-cell ```
2023-06-30 13:38:16 +01:00
version = "0.12.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"bitflags 2.3.3",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"bytes",
"caret",
tor-cell: Make RelayEarly a separate type. This allows us to remove a shenanigan from `restricted_msg!{}`.
2023-02-08 12:41:17 +00:00
"derive_more",
Replace manual Debug impl with educe in tor-cell
2022-03-02 15:41:01 +00:00
"educe",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"hex",
"hex-literal",
tor-cell: Macro to generate restricted RelayMsg and ChanMsg. This is the main implementation part of #525.
2023-02-06 15:51:39 +00:00
"paste",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"thiserror",
Move skip_fmt into tor-basic-utils Code motion and the minimal mechanical changes. As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/375#note_2783078
2022-03-04 11:42:49 +00:00
"tor-basic-utils",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-bytes",
"tor-cert",
tor-cell: provide HasKind. Additionally, refactor the IoError out of tor_cell::Error: nothing in TorCell created this; it was only used by tor_proto. This required refactoring in tor_proto to use a new error type. Here I decided to use a new CodecError for now, though we may refactor that away soon too.
2022-02-11 17:17:11 +00:00
"tor-error",
Sketch out new required APIs in tor-cell
2023-01-04 18:10:32 +00:00
"tor-hscrypto",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-linkspec",
"tor-llcrypto",
tor-cell: PaddingNegotiate::start: take IntegerMilliseconds
2022-08-08 15:58:32 +01:00
"tor-units",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "tor-cert"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.7.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Complete our migration to base64ct. This is in lieu of upgrading to the latest base64 crate, which has a different API from the old one. Since we have to migrate either way, we might as well use base64ct everywhere. I don't think that most of these cases _require_ constant-time base64, but it won't hurt.
2023-01-19 19:50:07 +00:00
"base64ct",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"caret",
Implement functionality to construct signed Ed25519 certs. This is behind a feature flag, since it isn't needed for pure clients: only onion services and relays need this. I've named the object that constructs these certs `Ed25519CertConstructor` because it doesn't follow the builder pattern exactly: mainly because you can't get an Ed25519Cert out of it. _That_ part is necessary because we require that an Ed25519Cert should only exist if the certificate was found to be well-signed with the right public key. Closes #511.
2022-06-29 17:48:22 +01:00
"derive_builder_fork_arti",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"hex-literal",
Tackling issue #663 (Use humantime in tests)
2022-12-12 17:41:22 +00:00
"humantime 2.1.0",
Implement functionality to construct signed Ed25519 certs. This is behind a feature flag, since it isn't needed for pure clients: only onion services and relays need this. I've named the object that constructs these certs `Ed25519CertConstructor` because it doesn't follow the builder pattern exactly: mainly because you can't get an Ed25519Cert out of it. _That_ part is necessary because we require that an Ed25519Cert should only exist if the certificate was found to be well-signed with the right public key. Closes #511.
2022-06-29 17:48:22 +01:00
"rand 0.8.5",
Upgrade to latest rsa crate.
2023-01-19 20:22:18 +00:00
"signature 1.6.4",
tor-proto: split and elaborate tor_bytes::Error instances Some of these were for decoding particular objects (we now say what kind of objects), and some were unrelated tor_cert errors that for some reason we had shoved into a tor_bytes::Error. There is now a separate tor_cert::CertError type, independent from tor_cert's use of `tor_bytes::Error` for parsing errors.
2022-06-23 20:42:45 +01:00
"thiserror",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-bytes",
"tor-checkable",
"tor-llcrypto",
]
[[package]]
name = "tor-chanmgr"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.9.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"async-trait",
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_fork_arti",
tor-chanmgr: Add bootstrap/status reporting. 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.
2022-01-17 22:11:18 +00:00
"derive_more",
Replace manual Debug impl with educe in tor-chanmgr
2022-03-02 17:10:47 +00:00
"educe",
Upgrade to float_eq 1.0.0
2022-06-16 13:39:03 +01:00
"float_eq",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"futures",
"futures-await-test",
"hex-literal",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
tor-chanmgr: Add bootstrap/status reporting. 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.
2022-01-17 22:11:18 +00:00
"postage",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
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
"safelog",
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",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"thiserror",
Move skip_fmt into tor-basic-utils Code motion and the minimal mechanical changes. As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/375#note_2783078
2022-03-04 11:42:49 +00:00
"tor-basic-utils",
channel padding: Send negotiation cells
2022-08-02 12:48:39 +01:00
"tor-cell",
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
"tor-config",
tor-error: Add as a ddpendency to many crates Doing this here makes it easier when I rebase/reorder things
2022-02-03 19:06:59 +00:00
"tor-error",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-linkspec",
"tor-llcrypto",
channel padding: Plumb settings from chanmgr
2022-06-14 15:42:23 +01:00
"tor-netdir",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-proto",
"tor-rtcompat",
"tor-rtmock",
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
"tor-socksproto",
channel padding: Use IntegerMilliseconds in padding::Parameters
2022-06-16 17:44:09 +01:00
"tor-units",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tracing",
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",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "tor-checkable"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.5.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Improve error messages in tor-checkable.
2022-06-22 14:48:42 +01:00
"humantime 2.1.0",
Upgrade to latest rsa crate.
2023-01-19 20:22:18 +00:00
"signature 1.6.4",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"thiserror",
"tor-llcrypto",
]
[[package]]
name = "tor-circmgr"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.9.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
HS configuration: Add retry parameters to configuration I think these should go in `[circuit_timing]`. That section already has some retry parameters, so is not strictly *timing*. This is not honoured yet.
2023-06-23 16:58:08 +01:00
"amplify",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"async-trait",
"bounded-vec-deque",
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
"derive_builder_fork_arti",
tor-circmgr: Provide testing feature and TestConfig Like the similar thing in tor-guardmgr.
2023-02-23 17:24:43 +00:00
"derive_more",
use downcast-rs instead of our own AsAny
2022-03-12 10:10:00 +00:00
"downcast-rs",
replace Arc with Box and use dyn-clone this also removes JoinResult
2022-03-12 17:33:25 +00:00
"dyn-clone",
Replace manual Debug impl with educe in tor-circmgr
2022-03-02 14:32:29 +00:00
"educe",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"futures",
"futures-await-test",
"humantime-serde",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
Turn FallbackList into a real type, and store one in GuardMgr. The guard manager is responsible for handing out the first hops of tor circuits, keeping track of their successes and failures, and remembering their states. Given that, it makes sense to store this information here. It is not yet used; I'll be fixing that in upcoming commits. Arguably, this information no longer belongs in the directory manager: I've added a todo about moving it. This commit will break compilation on its own in a couple of places; subsequent commits will fix it up.
2022-03-25 20:44:12 +00:00
"once_cell",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"pin-project",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"retry-error",
Apply `sensitive` in some info-level log messages. This specifically applies the `sensitive` wrapper in the places where we're logging target addresses at level "info" or higher.
2022-05-03 00:44:12 +01:00
"safelog",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"serde",
"static_assertions",
"thiserror",
Move skip_fmt into tor-basic-utils Code motion and the minimal mechanical changes. As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/375#note_2783078
2022-03-04 11:42:49 +00:00
"tor-basic-utils",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-chanmgr",
Move top-level configuration downwards from `arti` to `arti-config`. 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.
2021-11-17 19:16:55 +00:00
"tor-config",
tor-error: Add as a ddpendency to many crates Doing this here makes it easier when I rebase/reorder things
2022-02-03 19:06:59 +00:00
"tor-error",
Add a GuardMgr member to CircuitBuilder
2021-10-10 17:24:48 +01:00
"tor-guardmgr",
CircMgr: Draft APIs used to implement onion service clients.
2023-01-12 15:05:55 +00:00
"tor-hscrypto",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-linkspec",
"tor-llcrypto",
"tor-netdir",
"tor-netdoc",
"tor-persist",
"tor-proto",
"tor-rtcompat",
"tor-rtmock",
"tracing",
circmgr: Declare builder() unconditionally. (Still, only expose it when experimental-api is enabled.)
2023-03-16 17:06:18 +00:00
"visibility",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"weak-table",
]
[[package]]
name = "tor-config"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.9.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
CfgPath: Overhaul API Document that this can contain either a string for expansion, or a literal PathBuf not for expansion. Rename the `from_path` method to `new_literal`: a very important difference is whether it gets expanded - less important than the Rust type. Also, now it takes `Into<PathBuf>`, which avoids a needless clone. (We don't change the API in `arti-client` because `&tempfile::Tempdir()` doesn't implement `Into<PathBuf>`, so `arti-client` has to have some new `as_ref` calls.) Provide accessors `as_unexpanded_str` and `as_literal_path`. The deserialisation already makes this part of the stable API,l so not pvoding accessors seems just obstructive. They are useful for tests, too. Add tests for the new entrypoints, and for deserialisation of both variants from TOML (via config, or directly) and JSON.
2022-04-27 16:56:36 +01:00
"config",
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
"derive_builder_fork_arti",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"directories",
Update to shellexpand 3.1.0 so we can use dirs 5 everywhere Results of precisely cargo update -p shellexpand Incorporates changes I have made to shellexpand to allow use of dirs 4 *or* dirs 5.
2023-03-24 11:30:14 +00:00
"dirs",
list_builder: Use Educe to derive Default This allows us to use this with an item builder type which doesn't impl Default. (Obviously this only makes sense for items which aren't actually builders.)
2022-05-04 16:09:22 +01:00
"educe",
tor-config: Provide misc::Listen
2022-08-23 14:19:28 +01:00
"either",
arti-config abolition: Add deps to tor-config These are needed to support the code which is moving.
2022-05-13 11:27:10 +01:00
"fs-mistrust",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"once_cell",
Add dependency on paste crate The list accessor macro is going to want this.
2022-04-29 18:36:26 +01:00
"paste",
arti-config: Move cmdline to tor-config This does not know anything about arti, only about TOML and Config. Code motion, plus necessary import adjustments.
2022-05-11 11:22:22 +01:00
"regex",
CfgPath: Test serialisation round-trip with a binary format Use MessagePack. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
2022-04-27 16:35:55 +01:00
"rmp-serde",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"serde",
tor-config: Support functions for tracking ignored config keys This turns out to need quite a complicated algorithm.
2022-05-24 19:35:00 +01:00
"serde_ignored",
CfgPath: Overhaul API Document that this can contain either a string for expansion, or a literal PathBuf not for expansion. Rename the `from_path` method to `new_literal`: a very important difference is whether it gets expanded - less important than the Rust type. Also, now it takes `Into<PathBuf>`, which avoids a needless clone. (We don't change the API in `arti-client` because `&tempfile::Tempdir()` doesn't implement `Into<PathBuf>`, so `arti-client` has to have some new `as_ref` calls.) Provide accessors `as_unexpanded_str` and `as_literal_path`. The deserialisation already makes this part of the stable API,l so not pvoding accessors seems just obstructive. They are useful for tests, too. Add tests for the new entrypoints, and for deserialisation of both variants from TOML (via config, or directly) and JSON.
2022-04-27 16:56:36 +01:00
"serde_json",
Update shellexpand, and switch to non-fork Now we have bus>1 ownership of the crate name `shellexpand`. I have made a release, and retired `shellexpand-fork`. The new shellexpand release switches to a (quite similarly) unforked version of `dirs`.
2022-08-05 15:36:47 +01:00
"shellexpand",
tor-config: Introduce PaddingLevel This will be used for controlling channel padding, for now.
2022-07-27 16:01:59 +01:00
"strum",
arti-config abolition: Add deps to tor-config These are needed to support the code which is moving.
2022-05-13 11:27:10 +01:00
"tempfile",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"thiserror",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"toml 0.7.5",
config list-builder: Allow overriding the per-item build method This will be useful especially for simple lists where the entry doesn't need a separate builder type.
2022-04-25 13:36:13 +01:00
"tor-basic-utils",
tor-config: Add HasKind support. This required a few new ErrorKinds.
2022-02-09 14:25:11 +00:00
"tor-error",
Sketch API for reconfiguration. This patch doesn't actually make anything reconfigurable, but it does create an API that will tell you "you can't change the value of that!" If the API looks reasonable, I can start making it possible to change the values of individual items.
2021-12-06 18:54:53 +00:00
"tracing",
Add a few tests to tor-config.
2021-12-08 00:52:49 +00:00
"tracing-test",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
tor-congestion: implement the RTT estimation algorithm from prop#324 This commit implements the round-trip-time estimation algorithm from Tor proposal 324, validating the implementation against the test vectors found in C tor. (Note that at the time of writing, the new test vectors may not be committed to C tor yet, but they will be soon.) This also adds the necessary consensus parameters to `NetParameters`. Some of them have been renamed in order to (hopefully) make them more understandable.
2022-05-24 12:52:11 +01:00
[[package]]
name = "tor-congestion"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.5.2"
tor-congestion: implement the RTT estimation algorithm from prop#324 This commit implements the round-trip-time estimation algorithm from Tor proposal 324, validating the implementation against the test vectors found in C tor. (Note that at the time of writing, the new test vectors may not be committed to C tor yet, but they will be soon.) This also adds the necessary consensus parameters to `NetParameters`. Some of them have been renamed in order to (hopefully) make them more understandable.
2022-05-24 12:52:11 +01:00
dependencies = [
"thiserror",
"tor-error",
"tor-netdir",
"tor-units",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "tor-consdiff"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.5.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"hex",
"thiserror",
"tor-llcrypto",
]
[[package]]
name = "tor-dirclient"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.7.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"async-compression",
Complete our migration to base64ct. This is in lieu of upgrading to the latest base64 crate, which has a different API from the old one. Since we have to migrate either way, we might as well use base64ct everywhere. I don't think that most of these cases _require_ constant-time base64, but it won't hurt.
2023-01-19 19:50:07 +00:00
"base64ct",
DirMgr: Improve display for DocSource (Also, implement Display for tor_dirclient::SourceInfo).
2022-05-12 16:40:23 +01:00
"derive_more",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"futures",
"futures-await-test",
"hex",
"http",
"httparse",
"httpdate",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"memchr",
"thiserror",
"tor-circmgr",
Implement HasKind for tor_dirclient::Error
2022-02-16 19:53:58 +00:00
"tor-error",
tor-dirclient: Provide HsDescDownloadRequest In my tests this seems to do the right thing, but I'm getting 404s. I'm not sure if actually this URL is wrong.
2023-03-28 15:08:15 +01:00
"tor-hscrypto",
dirclient: Remember the source of each resposne we receive.
2022-03-18 14:11:27 +00:00
"tor-linkspec",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-llcrypto",
"tor-netdoc",
"tor-proto",
"tor-rtcompat",
"tor-rtmock",
"tracing",
]
[[package]]
name = "tor-dirmgr"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.10.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
bridge descriptors: Tests
2022-10-31 14:13:17 +00:00
"anyhow",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"async-trait",
Complete our migration to base64ct. This is in lieu of upgrading to the latest base64 crate, which has a different API from the old one. Since we have to migrate either way, we might as well use base64ct everywhere. I don't think that most of these cases _require_ constant-time base64, but it won't hurt.
2023-01-19 19:50:07 +00:00
"base64ct",
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
"derive_builder_fork_arti",
dirmgr: Remember where netdocs came from. This isn't complete (see TODO), but it's enough to let us report the right ErrorKind if something fails to parse.
2022-02-16 21:28:23 +00:00
"derive_more",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
Replace manual Debug impl with educe in tor-dirmgr
2022-03-02 17:13:18 +00:00
"educe",
Refactor directory events to use a FlagPublisher mechanism. This approach tries to preserve the current interface, but uses a counter-based event backend to implement a coalescing stream of events that can be represented as small integers. The advantage here is that publishing events no longer needs to be a blocking operation, since there is no queue to fill up.
2021-12-09 19:10:41 +00:00
"event-listener",
Upgrade to float_eq 1.0.0
2022-06-16 13:39:03 +01:00
"float_eq",
arti-client: Configure and use fs-mistrust. This is derived from the environment, not the configuration file: We might not want to trust the configuration file until we've decided whether we like its permissions.
2022-05-03 19:58:03 +01:00
"fs-mistrust",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"fslock",
"futures",
"hex",
"hex-literal",
bridge desc: Implement cache reuse logic and if-modified-since This introduces the new API functions to Store. But currently they are all no-ops. So all this machinery doesn't actually do anything. Also, it changes the API to the mockable downloader, to allow it to support if-modified-since. So this isn't used either. But it is more convenient to do this all at once in BridgeDescManager, since care needs to be taken about the intraction between if-modified-since and the persistent cache.
2022-11-04 19:00:43 +00:00
"humantime 2.1.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"humantime-serde",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"memmap2",
Tests for tor-dirmgr::bootstrap
2021-11-11 13:58:48 +00:00
"once_cell",
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
"paste",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"postage",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"retry-error",
"rusqlite",
bridge descs: Apply sensitive() to bridge identity in error log msg
2022-11-08 13:19:00 +00:00
"safelog",
DirMgr: Use scopeguard crate in place of ad hoc RAII substitutes
2022-06-10 18:54:30 +01:00
"scopeguard",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"serde",
Upgrade to latest rsa crate.
2023-01-19 20:22:18 +00:00
"signature 1.6.4",
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
"strum",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tempfile",
"thiserror",
Migrate tor-dirmgr from chrono to time 0.3 (This appears to be the emerging consensus of how to handle RUSTSEC-2020-0159.)
2021-10-24 15:50:21 +01:00
"time",
Move skip_fmt into tor-basic-utils Code motion and the minimal mechanical changes. As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/375#note_2783078
2022-03-04 11:42:49 +00:00
"tor-basic-utils",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-checkable",
"tor-circmgr",
Move top-level configuration downwards from `arti` to `arti-config`. 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.
2021-11-17 19:16:55 +00:00
"tor-config",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-consdiff",
"tor-dirclient",
tor-error: Add as a ddpendency to many crates Doing this here makes it easier when I rebase/reorder things
2022-02-03 19:06:59 +00:00
"tor-error",
Move fallback.rs into guardmgr. This is the logical place for it, I think: the GuardMgr's job is to pick the first hop for a circuit depending on remembered status for possible first hops. Making this change will let us streamline the code that interacts with these objects.
2022-03-25 17:38:01 +00:00
"tor-guardmgr",
bridge descriptors: Tests
2022-10-31 14:13:17 +00:00
"tor-linkspec",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-llcrypto",
"tor-netdir",
"tor-netdoc",
bridge descriptors: Provide an implementation of BridgeDescProvider Tests will come in a moment.
2022-10-18 20:00:27 +01:00
"tor-proto",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-rtcompat",
tor-dirmgr/state.rs: feed through additional parameters, use them - The additional parameters passed to GetConsensusState are now passed through all the states, and used as well. - WriteNetDir doesn't have a now() or config() method any more, since the states now get this from the runtime or the config parameters. - This required modifying the tests to make a mocked runtime and custom config directly, instead of using DirRcv for this purpose. - Additionally, because we don't have to upgrade a weak reference for DirState::dl_config(), that function no longer wraps its return value in Result. - (A bunch of the FIXMEs from the previous commit that introduced the additional parameters have now been rectified as a result.)
2022-05-04 16:48:44 +01:00
"tor-rtmock",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tracing",
bridge desc tests: Apply tracing_test::traced_test This lets us see the log messages. They look fine, as it happens.
2022-11-04 17:13:29 +00:00
"tracing-test",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
tor-error: Skeleton for new crate As per doc/Errors.md. Currently there are no error kinds. Some will be added as we go along.
2022-01-12 17:16:18 +00:00
[[package]]
name = "tor-error"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.5.2"
tor-error: Skeleton for new crate As per doc/Errors.md. Currently there are no error kinds. Some will be added as we go along.
2022-01-12 17:16:18 +00:00
dependencies = [
tor-error: Introduce InternalError as a type and a kind This can contain a backtrace, which will be printed.
2022-01-21 14:57:09 +00:00
"backtrace",
tor-error: Skeleton for new crate As per doc/Errors.md. Currently there are no error kinds. Some will be added as we go along.
2022-01-12 17:16:18 +00:00
"derive_more",
spawn errors: impl HasKind for futures::SpawnError This needs two kinds. We have decided to treat a non-shutdown SpawnError as "unexplained" rather than as an InternalError. There are many crates whose From<futures::task::SpawnError> for Error erroneously treat it as an internal error. We will fix them in a moment.
2022-01-21 15:45:41 +00:00
"futures",
tor-error: Add a new RetryTime type and related trait.
2022-03-31 15:43:46 +01:00
"once_cell",
tor-error: tracing module: Use macro to generate macros This abolishes some quintuplication. The output is identical except that: * The syntax display in the rustdoc output for the resulting macros seems to have somewhat less whitepsace. * The whimsical error messages in the examples are all identical. Ah well.
2023-07-07 17:43:26 +01:00
"paste",
event_report: assert correctness of format ending (Also, document that this static assertion is the reason why you are seeing a confusing error message.)
2023-07-07 13:47:49 +01:00
"static_assertions",
RetryTime: use strum::EnumDiscriminants to simplify loose_cmp. Also add tests for RetryTime comparison functions to make sure they work as expected.
2022-04-04 15:58:40 +01:00
"strum",
spawn errors: impl HasKind for futures::SpawnError This needs two kinds. We have decided to treat a non-shutdown SpawnError as "unexplained" rather than as an InternalError. There are many crates whose From<futures::task::SpawnError> for Error erroneously treat it as an internal error. We will fix them in a moment.
2022-01-21 15:45:41 +00:00
"thiserror",
tor-error: Add optional tracing support The main contribution here is a set of convenience macros for logging error `Report`s. Notably, this macros always logs `Internal` and `BadAspiUsage` errors at `WARN`, unless they are already at `ERROR` or more. This is a little tricky because `tracing::event!()` requires its Level argument to be a constant.
2023-07-06 18:48:01 +01:00
"tracing",
tor-error: Skeleton for new crate As per doc/Errors.md. Currently there are no error kinds. Some will be added as we go along.
2022-01-12 17:16:18 +00:00
]
Initial cut at a typed event framework for arti (arti#230). This implements a basic typed event broadcast mechanism, as described in arti#230: consumers of the new `tor-events` crate can emit `TorEvent` events, which others can consume via the `TorEventReceiver`. Under the hood, the crate uses the `async-broadcast` (https://github.com/smol-rs/async-broadcast) crate, and a `futures::mpsc::UnboundedSender` for the event emitters; these are glued together in the `EventReactor`, which must be run in a background thread for things to work. (This is done so event sending is always cheap and non-blocking, since `async-broadcast` senders don't have this functionality.) Additionally, the `TorEventKind` type is used to implement selective event reception / emission: receivers can subscribe to certain event types (and in fact start out receiving nothing), which filters the set of events they receive. Having no subscribers for a given event type means it won't even be emitted in the first place, making things more efficient.
2021-11-16 15:21:47 +00:00
[[package]]
name = "tor-events"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.5.2"
Initial cut at a typed event framework for arti (arti#230). This implements a basic typed event broadcast mechanism, as described in arti#230: consumers of the new `tor-events` crate can emit `TorEvent` events, which others can consume via the `TorEventReceiver`. Under the hood, the crate uses the `async-broadcast` (https://github.com/smol-rs/async-broadcast) crate, and a `futures::mpsc::UnboundedSender` for the event emitters; these are glued together in the `EventReactor`, which must be run in a background thread for things to work. (This is done so event sending is always cheap and non-blocking, since `async-broadcast` senders don't have this functionality.) Additionally, the `TorEventKind` type is used to implement selective event reception / emission: receivers can subscribe to certain event types (and in fact start out receiving nothing), which filters the set of events they receive. Having no subscribers for a given event type means it won't even be emitted in the first place, making things more efficient.
2021-11-16 15:21:47 +00:00
dependencies = [
"async-broadcast",
"futures",
"once_cell",
"serde",
"thiserror",
"tokio",
"tracing",
]
tor-geoip: Add new crate with GeoIP database functionality - This adds a new crate, `tor-geoip`, which can parse and perform lookups in the GeoIP database C-tor already uses (generated by a maintenance utility in the C-tor codebase). - We embed a copy of C-tor's databases with the crate and use `include_str!` to ship them with the binary, bloating its size somewhat. - This does, however, solve the problem of figuring out how to distribute these. - The plan is to gate this functionality behind a feature flag anyway, so the cost should be nil unless explicitly opted into. Part of tpo/core/onionmasq#47.
2023-06-13 15:27:14 +01:00
[[package]]
name = "tor-geoip"
version = "0.1.0"
dependencies = [
geoip: Make ?? a little more bullet-proof We want to make sure that ?? is always None, never a CountryCode.
2023-06-20 19:15:17 +01:00
"derive_more",
tor-geoip: Add new crate with GeoIP database functionality - This adds a new crate, `tor-geoip`, which can parse and perform lookups in the GeoIP database C-tor already uses (generated by a maintenance utility in the C-tor codebase). - We embed a copy of C-tor's databases with the crate and use `include_str!` to ship them with the binary, bloating its size somewhat. - This does, however, solve the problem of figuring out how to distribute these. - The plan is to gate this functionality behind a feature flag anyway, so the cost should be nil unless explicitly opted into. Part of tpo/core/onionmasq#47.
2023-06-13 15:27:14 +01:00
"once_cell",
"rangemap",
"thiserror",
"tor-error",
]
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
[[package]]
name = "tor-guardmgr"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.9.2"
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
dependencies = [
Complete our migration to base64ct. This is in lieu of upgrading to the latest base64 crate, which has a different API from the old one. Since we have to migrate either way, we might as well use base64ct everywhere. I don't think that most of these cases _require_ constant-time base64, but it won't hurt.
2023-01-19 19:50:07 +00:00
"base64ct",
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
"derive_builder_fork_arti",
Use derive_more to derive AsRef.
2022-03-29 20:16:35 +01:00
"derive_more",
tor-guardmgr: descs: Make BridgeDescError DynClone
2022-10-21 16:22:04 +01:00
"dyn-clone",
Replace manual Debug impl with educe in tor-guardmgr
2022-03-02 14:47:50 +00:00
"educe",
Upgrade to float_eq 1.0.0
2022-06-16 13:39:03 +01:00
"float_eq",
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
"futures",
Initial functions to determine and expose a clock skew estimate. (This is just a placeholder; I'm going to make the functions smarter in the next commit.)
2022-04-07 17:16:13 +01:00
"humantime 2.1.0",
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
"humantime-serde",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
BridgeDescProvider: Make BridgeDescEvent repr(u16) and derive traits This will enable us to impl FlagEvent for it.
2022-10-24 18:59:49 +01:00
"num_enum",
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
"pin-project",
GuardMgr: publish skew estimates. Instead of just having a function that recalculates the latest clock skew, instead recalculate the clock skew when it may have changed, and notify other processes via a postage::watch.
2022-04-11 20:13:48 +01:00
"postage",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
"retain_mut",
GuardMgr: Log when a guard status changes (significantly). We previously had a trace message on _every_ change. That's fine, but we also want to log more important changes where the user can see them. Namely: * If we go from any other status to Reachable, we want to tell the user. (We don't want to spam them if it was already reachable.) * If we go from Untried or Reachable to Unreachable, we want to tell the user. (We don't tell them about changes from Retriable to Unreachable, since that just means that a retry attempt was not successful.) Closes #627.
2022-11-17 17:32:57 +00:00
"safelog",
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
"serde",
BridgeConfigBuilder: Introduce the struct with the dictionary repr This struct is going to be the principal "dictionary-style" serde representation for a bridge, and the builder, making this all in keeping with our usual approach. In this commit: * Introduce the struct (defining the serialisation) * Provide the setters (defining the Rust API) * Add success test cases (not all of the data in which is used yet)
2022-11-18 16:32:11 +00:00
"serde_json",
guardmgr: Add bridges sample, encode sample ID in FirstHopId. The most important part of this commit is to make sure that each `FirstHopId` includes the `GuardSetSelector` from which the guard was selected. Doing this lets us be certain that when we report that a guard has succeeded or failed, we're reporting it in the right context. Additionally, this commit uses strum to make an iterator over the samples, so that we can make sure that our "for each sample" code is robust against future changes, and we don't miss the bridge sample.
2022-10-19 22:40:17 +01:00
"strum",
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
"thiserror",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"toml 0.7.5",
Move skip_fmt into tor-basic-utils Code motion and the minimal mechanical changes. As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/375#note_2783078
2022-03-04 11:42:49 +00:00
"tor-basic-utils",
Move top-level configuration downwards from `arti` to `arti-config`. 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.
2021-11-17 19:16:55 +00:00
"tor-config",
spawn errors: impl HasKind for futures::SpawnError This needs two kinds. We have decided to treat a non-shutdown SpawnError as "unexplained" rather than as an InternalError. There are many crates whose From<futures::task::SpawnError> for Error erroneously treat it as an internal error. We will fix them in a moment.
2022-01-21 15:45:41 +00:00
"tor-error",
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
"tor-linkspec",
"tor-llcrypto",
"tor-netdir",
guardmgr::..::sample_test: Fix intermittent failure. This test should only fail very rarely (around 1/2.4e8) when guards are chosen from a list of 20 with uniform probability. But that wasn't what we were doing on the mock test network: we were choosing from a list of 10 viable guards, with nonuniform probability. As a fix, we change the test network probabilities so that the guards _are_ chosen with a uniform probability for this test, and we use a modified version of the test network where there are indeed 20 Guard-flagged relays with the required DirCache=2 protocol. Closes #276.
2022-01-10 20:54:23 +00:00
"tor-netdoc",
Implement persistent state for guard mgr
2021-10-06 20:35:14 +01:00
"tor-persist",
Use coarsetime to build an incoming traffic timestamp. We need this for the circuit timeout estimator (#57). It needs to know "how recently have we got some incoming traffic", so that it can tell whether a circuit has truly timed out, or whether the entire network is down. I'm implementing this with coarsetime, since we need to update these in response to every single incoming cell, and we need the timestamp operation to be _fast_. (This reinstates an earlier commit, f30b2280, which I reverted because we didn't need it at the time.) Closes #179.
2021-07-13 15:35:46 +01:00
"tor-proto",
BridgeRelay: Implement more traits. Also add a BridgeRelayWithDesc type (name tbd) to guarantee that a bridge relay really does have a known descriptor before you try to build a circuit with it.
2022-10-04 18:34:23 +01:00
"tor-protover",
Initial backend implementation for guard node manager. 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.
2021-09-10 16:18:24 +01:00
"tor-rtcompat",
"tor-units",
"tracing",
]
Add a new stub hsclient module to connect to onion services.
2023-01-12 16:54:57 +00:00
[[package]]
name = "tor-hsclient"
Bump minor versions on crates with breaking changes Done with: ``` cargo set-version --bump minor -p tor-hsclient cargo set-version --bump minor -p arti-rpcserver cargo set-version --bump minor -p tor-hscrypto cargo set-version --bump minor -p tor-cell ```
2023-06-30 13:38:16 +01:00
version = "0.3.0"
Add a new stub hsclient module to connect to onion services.
2023-01-12 16:54:57 +00:00
dependencies = [
"async-trait",
hsclient state: Split off MultikeyIsolatedMap
2023-02-28 17:37:31 +00:00
"derive_more",
hsclient: Use a generic to provide a mock for connect() This will allow us to test state.rs.
2023-02-24 12:57:37 +00:00
"educe",
hsclient state: Restructure using a scope to drop the mutex guard Explicit drops don't work. Instead, introduce a scope. We need two scopes, actually: one where we do the initial table wrangling, and one for the retries after relock. So we must put the meat in a closure so we can reuse it. And we must return the flow control as an enum. Bah, etc. Avoid reformatting this for the moment. This makes the delta legible...
2023-02-28 14:51:32 +00:00
"either",
hsclient: Implement connection attempt tracking state machine This compiles, but it cannot work yet. Nor can it conveniently be tested.
2023-02-24 12:21:04 +00:00
"futures",
tor-netdir: Update tests to parse the descriptor, make test consensus lifetime configurable. Signed-off-by: Gabriela Moldovan <gabi@torproject.org>
2023-04-26 18:25:05 +01:00
"humantime 2.1.0",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
hsclient: Implement connection attempt tracking state machine This compiles, but it cannot work yet. Nor can it conveniently be tested.
2023-02-24 12:21:04 +00:00
"postage",
tor-netdir: Shuffle the list of HS dirs used for downloading descriptors. We'll probably need the hsdir list to be shuffled deterministically for testing purposes (this might be desirable, for example, when we write a test for HS descriptor download retries). Signed-off-by: Gabriela Moldovan <gabi@torproject.org>
2023-04-27 17:34:22 +01:00
"rand 0.8.5",
Add a new stub hsclient module to connect to onion services.
2023-01-12 16:54:57 +00:00
"rand_core 0.6.4",
hs dirs: Initial cut at descriptor downloading There are many TODOs here. Some are questions; some are straightforward and can be done in followups. With this code, I am able to reach the eprintln! and todo! with curl --socks5-hostname localhost:9150 https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/
2023-04-03 12:49:22 +01:00
"retry-error",
"safelog",
hsclient: Implement connection attempt tracking state machine This compiles, but it cannot work yet. Nor can it conveniently be tested.
2023-02-24 12:21:04 +00:00
"slotmap",
hs dirs: Initial cut at descriptor downloading There are many TODOs here. Some are questions; some are straightforward and can be done in followups. With this code, I am able to reach the eprintln! and todo! with curl --socks5-hostname localhost:9150 https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/
2023-04-03 12:49:22 +01:00
"strum",
Add a new stub hsclient module to connect to onion services.
2023-01-12 16:54:57 +00:00
"thiserror",
hsclient state: Test most important code paths
2023-02-24 15:00:46 +00:00
"tokio",
hs connect: Test descriptor download
2023-04-03 14:46:46 +01:00
"tor-async-utils",
tor-netdir: Shuffle the list of HS dirs used for downloading descriptors. We'll probably need the hsdir list to be shuffled deterministically for testing purposes (this might be desirable, for example, when we write a test for HS descriptor download retries). Signed-off-by: Gabriela Moldovan <gabi@torproject.org>
2023-04-27 17:34:22 +01:00
"tor-basic-utils",
hsclient: Create a CircTarget from an IntroPointDesc. The main body of this function is written so that we can later use it to create a CircTarget from an INTRODUCE2 message.
2023-06-06 14:08:47 +01:00
"tor-bytes",
tor-hsclient: Implement rendezvous setup, and retry framework This contains code to: * Iterate over introduction points * Make multiple attempts to connect * Apply timeouts to the various phases of each attempt * Establish a rendezvous point * Represent errors that occur during the above It provides places to add: * Implementation of the INTRODUCE1/INTRODUCE_ACK handshake * Reception of RENDEZVOUS2 and actual end-to-end circuit establishment * Recording of the outcome of connection attempts via particular IPTs * Using previous IPT outcome information for selecting IPTs to try * Tests of the new code (although more mocking will probably be needed) Much of this code works with a fixed type ClientCirc rather than going via the Mockable traits. That is wrong, and it will be fixed later.
2023-06-08 15:48:19 +01:00
"tor-cell",
hsclient state: Provide one test
2023-02-23 16:38:38 +00:00
"tor-chanmgr",
hs desc: Record a Timebound<HsDesc> (but not really for now) We have a local alias of `HsDesc = String` which needs to be got rid of. But, right now the alternative would be to implement all the code for signature checking and decryption of an `HsDesc`, before we can make a test case for the downloader part.
2023-04-03 15:16:55 +01:00
"tor-checkable",
Add a new stub hsclient module to connect to onion services.
2023-01-12 16:54:57 +00:00
"tor-circmgr",
HS secret keys: Move aggregate/config to tor-hsclient Provide a more cookied "secret keys for use to connecting to a particular HS" type, with a builder. This wants to use config stuff, so oughtn't to be in tor-*crypto. The individual types remain there.
2023-02-24 12:19:45 +00:00
"tor-config",
hs dirs: Initial cut at descriptor downloading There are many TODOs here. Some are questions; some are straightforward and can be done in followups. With this code, I am able to reach the eprintln! and todo! with curl --socks5-hostname localhost:9150 https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/
2023-04-03 12:49:22 +01:00
"tor-dirclient",
hsclient: Implement connection attempt tracking state machine This compiles, but it cannot work yet. Nor can it conveniently be tested.
2023-02-24 12:21:04 +00:00
"tor-error",
hsclient state: Provide one test
2023-02-23 16:38:38 +00:00
"tor-guardmgr",
Add a new stub hsclient module to connect to onion services.
2023-01-12 16:54:57 +00:00
"tor-hscrypto",
keymgr: Move the HS client and service key specifiers out of tor-keymgr. The HS `HsClientSpecifier` and `HsClientSecretKeySpecifier` are moved to `tor-hsclient`. The HS service secret key specifier stubs are moved to `tor-hsservice`.
2023-06-13 11:29:27 +01:00
"tor-keymgr",
hs dirs: Initial cut at descriptor downloading There are many TODOs here. Some are questions; some are straightforward and can be done in followups. With this code, I am able to reach the eprintln! and todo! with curl --socks5-hostname localhost:9150 https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/
2023-04-03 12:49:22 +01:00
"tor-linkspec",
Add a new stub hsclient module to connect to onion services.
2023-01-12 16:54:57 +00:00
"tor-llcrypto",
"tor-netdir",
hs connect: Test descriptor download
2023-04-03 14:46:46 +01:00
"tor-netdoc",
hsclient state: Provide one test
2023-02-23 16:38:38 +00:00
"tor-persist",
Add a new stub hsclient module to connect to onion services.
2023-01-12 16:54:57 +00:00
"tor-proto",
"tor-rtcompat",
tor-netdir: Update tests to parse the descriptor, make test consensus lifetime configurable. Signed-off-by: Gabriela Moldovan <gabi@torproject.org>
2023-04-26 18:25:05 +01:00
"tor-rtmock",
hsclient: Implement connection attempt tracking state machine This compiles, but it cannot work yet. Nor can it conveniently be tested.
2023-02-24 12:21:04 +00:00
"tracing",
hsclient state: Test most important code paths
2023-02-24 15:00:46 +00:00
"tracing-test",
Add a new stub hsclient module to connect to onion services.
2023-01-12 16:54:57 +00:00
]
Create a new tor-hscrypto crate. This module has types and operations needed in multiple places for an onion service implementation. There are a bunch of TODO hs-crypto comments that we'll need to fill in.
2022-12-29 19:17:22 +00:00
[[package]]
name = "tor-hscrypto"
Bump minor versions on crates with breaking changes Done with: ``` cargo set-version --bump minor -p tor-hsclient cargo set-version --bump minor -p arti-rpcserver cargo set-version --bump minor -p tor-hscrypto cargo set-version --bump minor -p tor-cell ```
2023-06-30 13:38:16 +01:00
version = "0.3.0"
Create a new tor-hscrypto crate. This module has types and operations needed in multiple places for an onion service implementation. There are a bunch of TODO hs-crypto comments that we'll need to fill in.
2022-12-29 19:17:22 +00:00
dependencies = [
impl Display for HsId
2023-03-07 14:12:25 +00:00
"data-encoding",
hscrypto: Use derive_more, and derive Deref for public keys.
2023-01-25 18:48:40 +00:00
"derive_more",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
impl Display for HsId
2023-03-07 14:12:25 +00:00
"hex",
hscrypto: Implement hs_mac.
2023-01-19 14:12:53 +00:00
"hex-literal",
hscrypto: Add an implementation for TimePeriod This required some API tweaks, which is probably to be expected; these time periods are a wonky kind of thing.
2023-01-19 15:10:00 +00:00
"humantime 2.1.0",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
hscrypto: Add and use a macro to define all PK types.
2023-01-19 13:25:16 +00:00
"paste",
tor-hscrypto: implement Rng.gen() for RendCookie
2023-06-07 17:24:46 +01:00
"rand 0.8.5",
Create a new tor-hscrypto crate. This module has types and operations needed in multiple places for an onion service implementation. There are a bunch of TODO hs-crypto comments that we'll need to fill in.
2022-12-29 19:17:22 +00:00
"rand_core 0.6.4",
Impl Redactable for HsId
2023-03-07 16:31:35 +00:00
"safelog",
hscrypto: Add and use a macro to define all PK types.
2023-01-19 13:25:16 +00:00
"serde",
hscrypto: Implement key blinding. This implementation was made based on the specification, and then validated against itself, and against C Tor.
2023-01-19 17:28:29 +00:00
"signature 1.6.4",
Create a new tor-hscrypto crate. This module has types and operations needed in multiple places for an onion service implementation. There are a bunch of TODO hs-crypto comments that we'll need to fill in.
2022-12-29 19:17:22 +00:00
"thiserror",
hscrypto: Implement key blinding. This implementation was made based on the specification, and then validated against itself, and against C Tor.
2023-01-19 17:28:29 +00:00
"tor-basic-utils",
hscrypto: Make several types Readable+Writeable Specifically, RendCookie, Subcredential, HsId, and HsBlindId.
2023-02-27 17:31:31 +00:00
"tor-bytes",
New ErrorKind for invalid onion addresses Use this to emit HS_BAD_ADDRESS as appropriate.
2023-06-22 15:51:52 +01:00
"tor-error",
Create a new tor-hscrypto crate. This module has types and operations needed in multiple places for an onion service implementation. There are a bunch of TODO hs-crypto comments that we'll need to fill in.
2022-12-29 19:17:22 +00:00
"tor-llcrypto",
hs time handling: Make TimePeriod contain length as IntegerMinutes Locally, the only functional effect is that now we refuse to handle non-whole-number-of-minutes lengths - but since the consensus parameter can't represent those, there's no overall functional change.
2023-02-08 17:35:51 +00:00
"tor-units",
Create a new tor-hscrypto crate. This module has types and operations needed in multiple places for an onion service implementation. There are a bunch of TODO hs-crypto comments that we'll need to fill in.
2022-12-29 19:17:22 +00:00
]
Sketch an API for onion services.
2023-01-12 19:38:40 +00:00
[[package]]
name = "tor-hsservice"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.2.2"
Sketch an API for onion services.
2023-01-12 19:38:40 +00:00
dependencies = [
"async-trait",
"rand_core 0.6.4",
"thiserror",
"tor-circmgr",
"tor-hscrypto",
"tor-llcrypto",
"tor-netdir",
"tor-proto",
"tor-rtcompat",
]
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
[[package]]
name = "tor-keymgr"
version = "0.1.0"
dependencies = [
"derive_more",
keymgr: Use Box<dyn EncodableKey> instead of Box<dyn Any>. Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1337#note_2917701 This will make it harder to accidentally return the wrong value from `Keystore::get` (the returned value is now at least guaranteed to implement `EncodableKey`). Closes #937
2023-07-10 14:20:17 +01:00
"downcast-rs",
keymgr: Create a KeyStoreError trait for keystore errors. The new `BoxedError` type will replace `tor_keymgr::Error`. Part of #901
2023-06-20 15:29:15 +01:00
"dyn-clone",
keymgr: Add an error variant for fs_mistrust errors. This will be useful later, when `KeyMgr` will start validating permissions and paths.
2023-06-16 11:19:01 +01:00
"fs-mistrust",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.10.5",
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
"ssh-key",
keymgr: Add tests for ArtiNativeKeyStore::key_path.
2023-06-28 19:40:20 +01:00
"tempfile",
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
"thiserror",
"tor-error",
"tor-hscrypto",
"tor-llcrypto",
keymgr: Move FS operations out of ssh.rs This moves the filesystem calls from the `ssh` module to `ArtiNativeKeyStore`. While `ArtiNativeKeyStore` shouldn't be concerning itself with filesystem operations either, that refactoring will be tackled separately (see arti#899).
2023-06-16 17:03:53 +01:00
"zeroize",
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "tor-linkspec"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.8.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Parsing, encoding, and serde for RelayId. The formats used here are backward-compatible with those used by C tor and those used elsewhere in our code. We need a way to encode _both_ current kinds of identities as a string that tells you what kind of ID they are. Traditionally we have used hexadecimal, sometimes with a $, for RSA ids, and we have used base64 for Ed25519 IDs. We also introduce a new forward-compatible format for new identity keys in the future. (The new format is the key identity type, a colon, and the id encoded as base64.) We will use this new format _only_ when we need to encode identities in a way where it would be otherwise unclear what kind of key we are dealing with.
2022-08-03 22:38:05 +01:00
"base64ct",
linkspec: Add an "all_overlapping" accessor to ByRelayIds. Also, add a few tests for this and the other accessors. We'll need this accessor to find whether we have any channels to _any_ of the identities that we're trying to connect to.
2022-10-14 17:31:16 +01:00
"by_address",
linkspec: Make LinkSpecType public. This lets us check the type of an `EncodedLinkSpec` as well, and lets us remove an interface that took a raw u8.
2023-05-10 17:19:37 +01:00
"caret",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
Add builders for OwnedChanTarget/OwnedCircTarget This will become the preferred way to make one of these objects, and insulate us against future API changes.
2022-10-05 17:56:17 +01:00
"derive_builder_fork_arti",
Add a set of Identity-related types and accessors. I wonder if these types are correct. I think it makes sense to have a Ref type like this, rather than just using `&RelayId`, but it doesn't seems that I can make `RelayId` and `RelayIdRef` implement Borrow and ToOwned for one another, so maybe I've messed up.
2022-08-03 16:26:53 +01:00
"derive_more",
Create an API for TransportId
2022-09-22 13:40:01 +01:00
"educe",
Parsing, encoding, and serde for RelayId. The formats used here are backward-compatible with those used by C tor and those used elsewhere in our code. We need a way to encode _both_ current kinds of identities as a string that tells you what kind of ID they are. Traditionally we have used hexadecimal, sometimes with a $, for RSA ids, and we have used base64 for Ed25519 IDs. We also introduce a new forward-compatible format for new identity keys in the future. (The new format is the key identity type, a colon, and the id encoded as base64.) We will use this new format _only_ when we need to encode identities in a way where it would be otherwise unclear what kind of key we are dealing with.
2022-08-03 22:38:05 +01:00
"hex",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"hex-literal",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
tor-linkspec: Provide LoggedChanTarget type alias and utility method This makes it easy to talk about, and construct, a BoxSensitive<OwnedChanTarget>, which is what we'll use in errors.
2022-11-23 15:19:15 +00:00
"safelog",
Implement serde traits on RelayIds. This will allow RelayIds to replace IdPair in tor-guardmgr. (The fields are named accordingly with `serde(rename)`.)
2022-07-26 15:26:35 +01:00
"serde",
Write tests for RelayIdSet.
2022-10-15 15:06:02 +01:00
"serde_test",
Implement serde for PtTarget and its members. This will let us remember bridges that use pluggable transports.
2022-10-19 14:34:11 +01:00
"serde_with",
Add a set of Identity-related types and accessors. I wonder if these types are correct. I think it makes sense to have a Ref type like this, rather than just using `&RelayId`, but it doesn't seems that I can make `RelayId` and `RelayIdRef` implement Borrow and ToOwned for one another, so maybe I've messed up.
2022-08-03 16:26:53 +01:00
"strum",
Parsing, encoding, and serde for RelayId. The formats used here are backward-compatible with those used by C tor and those used elsewhere in our code. We need a way to encode _both_ current kinds of identities as a string that tells you what kind of ID they are. Traditionally we have used hexadecimal, sometimes with a $, for RSA ids, and we have used base64 for Ed25519 IDs. We also introduce a new forward-compatible format for new identity keys in the future. (The new format is the key identity type, a colon, and the id encoded as base64.) We will use this new format _only_ when we need to encode identities in a way where it would be otherwise unclear what kind of key we are dealing with.
2022-08-03 22:38:05 +01:00
"thiserror",
tor-linkspec: ByRelayIds<> type to hold a set of HasRelayIds This is based on the type generated with n_key_set, with a couple of extra methods to take advantage of RelayId and RelayIdRef.
2022-10-04 16:48:31 +01:00
"tor-basic-utils",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-bytes",
Add builders for OwnedChanTarget/OwnedCircTarget This will become the preferred way to make one of these objects, and insulate us against future API changes.
2022-10-05 17:56:17 +01:00
"tor-config",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-llcrypto",
"tor-protover",
]
[[package]]
name = "tor-llcrypto"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.5.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"aes",
Complete our migration to base64ct. This is in lieu of upgrading to the latest base64 crate, which has a different API from the old one. Since we have to migrate either way, we might as well use base64ct everywhere. I don't think that most of these cases _require_ constant-time base64, but it won't hurt.
2023-01-19 19:50:07 +00:00
"base64ct",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"cipher",
Upgrade to AES 0.8 Now that we require Rust 1.56, we can upgrade to AES 0.8. This forces us to have some slight API changes. We require cipher 0.4.1, not cipher 0.4.0, since 0.4.0 has compatibility issues with Rust 1.56.
2022-04-25 20:39:26 +01:00
"ctr",
Back down x25519-dalek to 2.0.0-pre.1 from 2.0.0-rc.2 ========================= Notes from nickm: (This differs from pinkforest's original MR: It removes the Cargo.lock changes and the version bump on tor-llcrypto.) Minimal Cargo.lock changes from downgrade. (These are exactly those changes generated by running "build" and "test".) There are several reasons to do this: * It's best to bump all of our dalek dependencies at once to rc.3 or later, rather than the piecemeal approach we've been stuck with so far. * We don't want to do this bump right now, since there are some tricky questions about clamping we need to figure out (see #808), and we need to make sure we get them right, and we're in a distracted this week. * We _do_ need to move away from 2.0.0-rc.2 right now, since it was causing a failure in `cargo install arti`, and then it got yanked. Thanks to pinkforest for helping us out here and explaining all of this! Fixes #926. Commit-edited-by: Nick Mathewson <nickm@torproject.org>
2023-06-27 01:45:36 +01:00
"curve25519-dalek",
Add builder for encoding hidden service descriptors. This introduces the `NetdocBuilder` trait described in `netdoc-builder.md` and a new `tor-netdoc::doc::hsdesc::build` module, which exports the `HsDescBuilder`. Hidden services will use `HsDescBuilder` to build and encode hidden service descriptors. There are several TODOs in the code that I'm planning to address separately. Partially addresses #745. Signed-off-by: Gabriela Moldovan <gabi@torproject.org>
2023-03-16 13:51:29 +00:00
"derive_more",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"ed25519-dalek",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"getrandom 0.2.10",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"hex",
"hex-literal",
add support for openssl backend in llcrypto
2022-05-28 19:55:23 +01:00
"openssl",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"rand_core 0.5.1",
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
"rand_core 0.6.4",
keymgr: Add ArtiNativeKeyStore implementation skeleton. This adds implementation stubs for `ArtiNativeKeyStore`, and introduces the traits needed to make the `KeyStore` APIs work.
2023-05-30 16:08:18 +01:00
"rsa 0.9.2",
linkspec: Give a Redacted form for chantarget.
2022-11-21 19:31:33 +00:00
"safelog",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"serde",
"serde_test",
Switch from sha-1 back to sha1. As near as I can tell, the rust-crypto SHA1 crate was called `sha-1` for a while because of a conflict with a different SHA1 crate. Now they apparently have the `sha1` name back and have deprecated the `sha-1` name.
2022-11-28 14:02:16 +00:00
"sha1",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"sha2 0.10.7",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"sha3",
Upgrade to latest rsa crate.
2023-01-19 20:22:18 +00:00
"signature 1.6.4",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"simple_asn1",
"subtle",
"thiserror",
Use testing_rng() in tests throughout our crates. This only affects uses of thread_rng(), and affects them all more or less indiscriminately. One test does not work with ARTI_TEST_PRNG=deterministic; the next commit will fix it.
2022-06-02 18:31:43 +01:00
"tor-basic-utils",
add support for openssl backend in llcrypto
2022-05-28 19:55:23 +01:00
"typenum",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"x25519-dalek",
"zeroize",
]
[[package]]
name = "tor-netdir"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.9.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"bitflags 2.3.3",
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
"derive_builder_fork_arti",
tor-netdir: Add RelayWeight type and accessors. I'm not thrilled with this code, but I think it's needed to implement guards correctly.
2021-09-16 19:23:41 +01:00
"derive_more",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
Upgrade to float_eq 1.0.0
2022-06-16 13:39:03 +01:00
"float_eq",
Make daemon tasks self-contained; introduce NetDirProvider The various background daemon tasks that `arti-client` used to spawn are now handled inside their respective crates instead, with functions provided to spawn them that return `TaskHandle`s. This required introducing a new trait, `NetDirProvider`, which steals some functionality from the `DirProvider` trait to enable `tor-circmgr` to depend on it (`tor-circmgr` is a dependency of `tor-dirmgr`, so it can't depend on `DirProvider` directly). While we're at it, we also make some of the tasks wait for events from the `NetDirProvider` instead of sleeping, slightly increasing efficiency.
2022-03-28 13:54:36 +01:00
"futures",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"hex",
netdir: Implement ring-param constructors and time period accessors This logic is a bit tricky, so I've tried to document it and add fairly good tests. The silver lining is that the external API for all of this logic will make it invisible and hidden. There are some cases where I added functions that I think might eventually get lowered into MdConsensus: But I don't want to lower too much right now, since the convention for our netdoc accessors is that they are fairly unsophisticated, and they show you the document as it is. Closes #686
2023-01-24 15:46:56 +00:00
"hex-literal",
"humantime 2.1.0",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
"num_enum",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
tor-netdir: Use reproducible RNG in tests. The rand crate's documentation says it's not okay to rely on StdRng having reproducible output. So instead, let's switch to ChaCha12Rng instead (which is what StrRng currently uses).
2021-12-06 20:06:34 +00:00
"rand_chacha 0.3.1",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"serde",
Upgrade to latest rsa crate.
2023-01-19 20:22:18 +00:00
"signature 1.6.4",
tor-netdir: Add a static assertion about RelayIdType::COUNT Doing this will make sure that we fix a correctness issue in netdir that will be caused if we add more IDs. (Also add RelayIdType::COUNT in tor-linkspec.)
2022-08-09 20:51:05 +01:00
"static_assertions",
FlagEvent trait: Implement using macros The explicit list of variant names, that needs to be kept in sync, and is a test failure semver break hazard, is now gone. All the necessary code is now generated automatically, and cannot be wrong. I want this because I find myself wanting to add a second implementation of FlagEvent, for another type.
2022-10-24 19:30:29 +01:00
"strum",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"thiserror",
netdir: Implement ring-param constructors and time period accessors This logic is a bit tricky, so I've tried to document it and add fairly good tests. The silver lining is that the external API for all of this logic will make it invisible and hidden. There are some cases where I added functions that I think might eventually get lowered into MdConsensus: But I don't want to lower too much right now, since the convention for our netdoc accessors is that they are fairly unsophisticated, and they show you the document as it is. Closes #686
2023-01-24 15:46:56 +00:00
"time",
Use testing_rng() in tests throughout our crates. This only affects uses of thread_rng(), and affects them all more or less indiscriminately. One test does not work with ARTI_TEST_PRNG=deterministic; the next commit will fix it.
2022-06-02 18:31:43 +01:00
"tor-basic-utils",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-checkable",
Move top-level configuration downwards from `arti` to `arti-config`. 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.
2021-11-17 19:16:55 +00:00
"tor-config",
Update arti-client to new NetDirProvider API. This allows us to give better errors in the case where bootstrapping succeeds at first, but fails thereafter for long enough to make our directory expire.
2022-07-25 17:06:37 +01:00
"tor-error",
Sketch APIs for the onion service directory ring. These are a bit complex internally, but the API they present is pretty simple. I've left some discussion of points where the design isn't totally fleshed out, and where we need to look harder at the spec. Part of #716.
2023-01-09 17:10:29 +00:00
"tor-hscrypto",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-linkspec",
"tor-llcrypto",
"tor-netdoc",
"tor-protover",
"tor-units",
"tracing",
tor-netdir: Use typed-index-collections for router status index
2023-02-01 19:14:07 +00:00
"typed-index-collections",
netdir: Conditionally expose some by_rsa APIs as experimental. Network-health wants these to see whether a given relay is listed in the consensus. cc @juga
2023-06-28 12:10:37 +01:00
"visibility",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "tor-netdoc"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.8.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
netdoc: Use derive amplify::Getters for HsDesc accessors. Closes #909.
2023-06-20 19:00:41 +01:00
"amplify",
netdoc: Use a dev-dependency on anyhow to fix a doc example
2023-06-22 18:42:40 +01:00
"anyhow",
Replace `base64` crate with `base64ct` crate Note: the `base64ct` crate rejects invalid characters when the decoding is done on padded strings. However, the `FromStr` impl for `B64` can have both padded **and** unpadded inputs, so all inputs are now padded first, before decoding.
2022-06-22 02:02:33 +01:00
"base64ct",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"bitflags 2.3.3",
netdoc: implement onion service descryptor encryption This is tested via a round-trip check, and via a successful decryption of our example descriptor's outer layer.
2023-01-30 19:16:41 +00:00
"cipher",
Add builder for encoding hidden service descriptors. This introduces the `NetdocBuilder` trait described in `netdoc-builder.md` and a new `tor-netdoc::doc::hsdesc::build` module, which exports the `HsDescBuilder`. Hidden services will use `HsDescBuilder` to build and encode hidden service descriptors. There are several TODOs in the code that I'm planning to address separately. Partially addresses #745. Signed-off-by: Gabriela Moldovan <gabi@torproject.org>
2023-03-16 13:51:29 +00:00
"derive_builder_fork_arti",
Refactor tor_netdoc::Error This error type doesn't impement HasKind, since the kind will depend on context. However, the existing implementation was pretty messy and inconsistent: Some errors had positions, some didn't. Some took messages as str, some as String. Some had internal errors that were somewhat orthogonal to their actual types. This commit refactors tor_netdoc::Error to use a ParseErrorKind, and adds a set of convenience functions to add positions and messages to the errors that need them.
2022-02-14 18:08:28 +00:00
"derive_more",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
tor-netdoc: Actually, make TokVal be a Vec This enum was otiose: its set of valid values is precisely those of a Vec. (Indeed what would TokVal::Multi(vec![]) have meant?)
2022-03-11 18:42:01 +00:00
"educe",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"hex",
"hex-literal",
Tackling issue #663 (Use humantime in tests)
2022-12-12 17:41:22 +00:00
"humantime 2.1.0",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"once_cell",
"phf",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"serde",
NetDoc: Make AddrPortPattern implement serde traits I'm using serde_with here to just re-use the Display and FromStr implementations, since those are what has proven easier to type in the past.
2022-06-09 21:52:52 +01:00
"serde_json",
"serde_with",
Upgrade to latest rsa crate.
2023-01-19 20:22:18 +00:00
"signature 1.6.4",
netdoc: Parse the inner layer of an onion service descriptor. There are some places where I note certificates which are not currently validated, because there is no cryptographic point in doing so. We should either document that this is okay, or validate the certificates anyway. This code might benefit from refactoring to make it prettier.
2023-01-31 15:27:45 +00:00
"smallvec",
netdoc: use ct_lookup for rend descriptor cookie lookup (I doubt that there is a viable side channel here, but still we might as well get in the habit of doing these things properly.)
2023-06-14 17:26:57 +01:00
"subtle",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"thiserror",
Migrate tor-dirmgr from chrono to time 0.3 (This appears to be the emerging consensus of how to handle RUSTSEC-2020-0159.)
2021-10-24 15:50:21 +01:00
"time",
netdoc: add a new type for Nicknames Relay nicknames are always between 1 and 19 characters long, and they're always ASCII: That means that storing them in a [u8;19] will always be possible, and always use less resources than storing them in a String. Fortunately, the tinystr crate already helps us with this kind of thing.
2022-03-10 21:38:23 +00:00
"tinystr",
netdoc: implement onion service descryptor encryption This is tested via a round-trip check, and via a successful decryption of our example descriptor's outer layer.
2023-01-30 19:16:41 +00:00
"tor-basic-utils",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-bytes",
"tor-cert",
"tor-checkable",
Refactor tor_netdoc::Error This error type doesn't impement HasKind, since the kind will depend on context. However, the existing implementation was pretty messy and inconsistent: Some errors had positions, some didn't. Some took messages as str, some as String. Some had internal errors that were somewhat orthogonal to their actual types. This commit refactors tor_netdoc::Error to use a ParseErrorKind, and adds a set of convenience functions to add positions and messages to the errors that need them.
2022-02-14 18:08:28 +00:00
"tor-error",
netdoc: Outline some basic types for encoding HsDescs.
2022-12-29 19:48:33 +00:00
"tor-hscrypto",
"tor-linkspec",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-llcrypto",
"tor-protover",
hsdesc: Use an IntegerMinutes<u16> to hold lifetime.
2023-02-08 18:33:07 +00:00
"tor-units",
tor-netdoc: Conditionally expose document fields. This commit uses the `visibility` and `visible` crates to conditionally make certain structs and their fields public (respectively). This is incredibly dangerous to use for anything besides testing, and I've tried to write the documentation for the feature accordingly.
2022-03-31 14:20:21 +01:00
"visibility",
"visible",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"weak-table",
netdoc: implement onion service descryptor encryption This is tested via a round-trip check, and via a successful decryption of our example descriptor's outer layer.
2023-01-30 19:16:41 +00:00
"zeroize",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "tor-persist"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.7.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
tor-persist: Big refactoring on Error type. Every error now has an action (what we were trying to do), a resource (what we were trying to do it to), and a source (what problem we encountered). Initially I tried to add "action" and "resource" fields to error variants individually, but that led to a combinatorial explosion. Part of #323.
2022-07-05 15:28:18 +01:00
"derive_more",
arti-client: Configure and use fs-mistrust. This is derived from the environment, not the configuration file: We might not want to trust the configuration file until we've decided whether we like its permissions.
2022-05-03 19:58:03 +01:00
"fs-mistrust",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"fslock",
"sanitize-filename",
"serde",
Change tor-persist to use json instead of toml. The limitations with toml seemed to be reaching a head, and I wasn't able to refactor the guardmgr code enough to actually have its state be serializable as toml. Json's limitations are much narrower.
2021-10-07 14:23:35 +01:00
"serde_json",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tempfile",
"thiserror",
tor-error: Add as a ddpendency to many crates Doing this here makes it easier when I rebase/reorder things
2022-02-03 19:06:59 +00:00
"tor-error",
Remove obsolete files from our state directory. This patch removes files created by older versions of arti, if they are at least 4 weeks old. Closes #282
2022-04-12 22:15:05 +01:00
"tracing",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "tor-proto"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.11.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"asynchronous-codec",
"bytes",
"cipher",
Use coarsetime to build an incoming traffic timestamp. We need this for the circuit timeout estimator (#57). It needs to know "how recently have we got some incoming traffic", so that it can tell whether a circuit has truly timed out, or whether the entire network is down. I'm implementing this with coarsetime, since we need to update these in response to every single incoming cell, and we need the timestamp operation to be _fast_. (This reinstates an earlier commit, f30b2280, which I reverted because we didn't need it at the time.) Closes #179.
2021-07-13 15:35:46 +01:00
"coarsetime",
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_fork_arti",
tor-cell: Refactor relay cells to copy much less We now manipulate raw relay cell bodies as (an alias for) `Box<[u8;509]>` rather than as (an alias for) `[u8;509]`. This enables us to do much less copying. It will become more important soon, as we defer parsing relay cell bodies even longer. Related to #7. We also use SliceWriter to avoid allocating a Vec<> for every relay message we want to encode, and instead encode directly into the cell.
2023-02-13 02:19:28 +00:00
"derive_more",
Run "cargo update".
2023-05-22 12:47:20 +01:00
"digest 0.10.7",
Replace manual Debug impls with educe in tor-proto We now print slighly more information.
2022-03-02 15:44:09 +00:00
"educe",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"futures",
"generic-array",
"hex",
"hex-literal",
"hkdf",
"hmac",
Tackling issue #663 (Use humantime in tests)
2022-12-12 17:41:22 +00:00
"humantime 2.1.0",
keymgr: Remove ArtiPath normalization, introduce additional restrictions.
2023-06-28 16:18:03 +01:00
"itertools 0.11.0",
tor-proto: channel: Provide padding::Timer
2022-06-06 18:39:49 +01:00
"pin-project",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
"rand_core 0.6.4",
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",
tor-proto: When relay IDs mismatch, the IDs are sensitive in errors
2022-12-12 13:35:49 +00:00
"safelog",
tor-proto: padding: Test padding timer distribution
2022-06-08 14:53:05 +01:00
"statrs",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"subtle",
"thiserror",
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
"tokio",
"tokio-util",
Move functionality from tor_basic_utils to tor_async_utils This commit is mostly code movement; I'd recommend reviewing it with git's `--color-moved` option.
2023-03-29 14:17:13 +01:00
"tor-async-utils",
Move skip_fmt into tor-basic-utils Code motion and the minimal mechanical changes. As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/375#note_2783078
2022-03-04 11:42:49 +00:00
"tor-basic-utils",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-bytes",
"tor-cell",
"tor-cert",
"tor-checkable",
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",
tor-proto: use InternalError for internal errors.
2022-02-11 20:20:50 +00:00
"tor-error",
hs_ntor: Use Subcredential type from tor-hscrypto
2023-05-17 13:28:57 +01:00
"tor-hscrypto",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-linkspec",
"tor-llcrypto",
"tor-protover",
tor-proto: Use tor-rtcompat macros for testing, not tokio. Closes #222.
2021-11-15 17:55:08 +00:00
"tor-rtcompat",
tor-proto: channel: Provide padding::Timer
2022-06-06 18:39:49 +01:00
"tor-rtmock",
channel padding: Use IntegerMilliseconds in padding::Parameters
2022-06-16 17:44:09 +01:00
"tor-units",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tracing",
"typenum",
tor-proto: Implement functionality to send a message and accept replies This new function combines "sending a message" and "accepting replies in a stream" into a single call, so that there is no gap between when the message is sent and the replies are available. There are a number of compromises here, in order to avoid API proliferation. I've tried to contain them as best I can. See comments for additional design discussion.
2023-03-03 17:11:34 +00:00
"visibility",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"zeroize",
]
[[package]]
name = "tor-protover"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.5.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"caret",
"thiserror",
]
Add the skeleton of a tor-ptmgr crate When complete, this crate will handle launching and using pluggable transports on demand.
2022-09-23 14:47:30 +01:00
[[package]]
name = "tor-ptmgr"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.3.2"
Add the skeleton of a tor-ptmgr crate When complete, this crate will handle launching and using pluggable transports on demand.
2022-09-23 14:47:30 +01:00
dependencies = [
tor-ptmgr/ipc: First cut of pluggable transport spawning The new `ipc` module inside `tor-ptmgr` implements the Pluggable Transport Specification version 1 (`pt-spec.txt`, https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/pt-spec.txt). This enables module users to spawn pluggable transport binaries inside a child process asynchronously, and receive structured information about how to connect to the transports provided by said binaries. Internally, this is structured as a pure set of serialisers and deserialisers for the protocol in the specification (in the form of environment variables, and the PT's stdout), a wrapper to run the PT binary and enable accessing its output asynchronously, and a user-facing wrapper that handles ensuring all the requested transports launched properly. The included `run-pt` example is an exceedingly minimal wrapper program that was useful in testing. More tests can and should be added in a further MR. closes arti#394; part of arti#69
2022-10-19 14:36:40 +01:00
"anyhow",
Add the skeleton of a tor-ptmgr crate When complete, this crate will handle launching and using pluggable transports on demand.
2022-09-23 14:47:30 +01:00
"async-trait",
tor-ptmgr/ipc: First cut of pluggable transport spawning The new `ipc` module inside `tor-ptmgr` implements the Pluggable Transport Specification version 1 (`pt-spec.txt`, https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/pt-spec.txt). This enables module users to spawn pluggable transport binaries inside a child process asynchronously, and receive structured information about how to connect to the transports provided by said binaries. Internally, this is structured as a pure set of serialisers and deserialisers for the protocol in the specification (in the form of environment variables, and the PT's stdout), a wrapper to run the PT binary and enable accessing its output asynchronously, and a user-facing wrapper that handles ensuring all the requested transports launched properly. The included `run-pt` example is an exceedingly minimal wrapper program that was useful in testing. More tests can and should be added in a further MR. closes arti#394; part of arti#69
2022-10-19 14:36:40 +01:00
"derive_builder_fork_arti",
ptmgr: Use anonymize_home when displaying paths in errors
2022-11-30 00:30:50 +00:00
"fs-mistrust",
Add the skeleton of a tor-ptmgr crate When complete, this crate will handle launching and using pluggable transports on demand.
2022-09-23 14:47:30 +01:00
"futures",
tor-ptmgr: make configuration use builders, plumb into arti-client This brings the draft configuration mechanisms in tor-ptmgr in line with the config in other crates, using builders. It also plumbs the config type through into the main `arti-client` config, and adds some example lines to `arti-example-config.toml`.
2022-11-03 14:36:31 +00:00
"serde",
tor-ptmgr/ipc: First cut of pluggable transport spawning The new `ipc` module inside `tor-ptmgr` implements the Pluggable Transport Specification version 1 (`pt-spec.txt`, https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/pt-spec.txt). This enables module users to spawn pluggable transport binaries inside a child process asynchronously, and receive structured information about how to connect to the transports provided by said binaries. Internally, this is structured as a pure set of serialisers and deserialisers for the protocol in the specification (in the form of environment variables, and the PT's stdout), a wrapper to run the PT binary and enable accessing its output asynchronously, and a user-facing wrapper that handles ensuring all the requested transports launched properly. The included `run-pt` example is an exceedingly minimal wrapper program that was useful in testing. More tests can and should be added in a further MR. closes arti#394; part of arti#69
2022-10-19 14:36:40 +01:00
"thiserror",
"tokio",
Add the skeleton of a tor-ptmgr crate When complete, this crate will handle launching and using pluggable transports on demand.
2022-09-23 14:47:30 +01:00
"tor-chanmgr",
"tor-config",
tor-ptmgr/ipc: First cut of pluggable transport spawning The new `ipc` module inside `tor-ptmgr` implements the Pluggable Transport Specification version 1 (`pt-spec.txt`, https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/pt-spec.txt). This enables module users to spawn pluggable transport binaries inside a child process asynchronously, and receive structured information about how to connect to the transports provided by said binaries. Internally, this is structured as a pure set of serialisers and deserialisers for the protocol in the specification (in the form of environment variables, and the PT's stdout), a wrapper to run the PT binary and enable accessing its output asynchronously, and a user-facing wrapper that handles ensuring all the requested transports launched properly. The included `run-pt` example is an exceedingly minimal wrapper program that was useful in testing. More tests can and should be added in a further MR. closes arti#394; part of arti#69
2022-10-19 14:36:40 +01:00
"tor-error",
Add the skeleton of a tor-ptmgr crate When complete, this crate will handle launching and using pluggable transports on demand.
2022-09-23 14:47:30 +01:00
"tor-linkspec",
"tor-rtcompat",
tor-ptmgr/ipc: First cut of pluggable transport spawning The new `ipc` module inside `tor-ptmgr` implements the Pluggable Transport Specification version 1 (`pt-spec.txt`, https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/pt-spec.txt). This enables module users to spawn pluggable transport binaries inside a child process asynchronously, and receive structured information about how to connect to the transports provided by said binaries. Internally, this is structured as a pure set of serialisers and deserialisers for the protocol in the specification (in the form of environment variables, and the PT's stdout), a wrapper to run the PT binary and enable accessing its output asynchronously, and a user-facing wrapper that handles ensuring all the requested transports launched properly. The included `run-pt` example is an exceedingly minimal wrapper program that was useful in testing. More tests can and should be added in a further MR. closes arti#394; part of arti#69
2022-10-19 14:36:40 +01:00
"tor-socksproto",
"tracing",
"tracing-subscriber",
ptmgr: Mark PtMessage and next_message as experimental-api. These are implementation details and we don't want to mark them as stable. To do this, I needed to apply some additional options to the example code's configuration in Cargo.toml.
2022-11-28 18:16:58 +00:00
"visibility",
Add the skeleton of a tor-ptmgr crate When complete, this crate will handle launching and using pluggable transports on demand.
2022-09-23 14:47:30 +01:00
]
Start on a lower-level tor-rpccmd crate. This crate will hold the backend pieces of RPC interaction that different parts of Arti get to implement.
2023-03-31 16:57:05 +01:00
[[package]]
Rename tor-rpccmd to tor-rpcbase.
2023-04-11 20:13:19 +01:00
name = "tor-rpcbase"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.1.2"
Start on a lower-level tor-rpccmd crate. This crate will hold the backend pieces of RPC interaction that different parts of Arti get to implement.
2023-03-31 16:57:05 +01:00
dependencies = [
RPC: Initial implementation of a multiple-argument dispatch This code uses some kludges (discussed with Ian previously and hopefully well documented here) to get a type-identifier for each type in a const context. It then defines a macro to declare a type-erased versions of a concrete implementation functions, and register those implementations to be called later. We will probably want to tweak a bunch of this code as we move ahead.
2023-04-03 15:23:55 +01:00
"assert-impl",
"downcast-rs",
rpc: Add Update functionality to rpc::Context. I'm not sure about these APIs at all! They force us to use `async_trait` for `tor_rpccmd::Context`, which bothers me. Should we just have a function that returns `Option<Box<dyn Sink<Item=X, Error=Y>>` or something? If so, what's the correct Y?
2023-04-03 22:20:47 +01:00
"erased-serde",
Start on a lower-level tor-rpccmd crate. This crate will hold the backend pieces of RPC interaction that different parts of Arti get to implement.
2023-03-31 16:57:05 +01:00
"futures",
"futures-await-test",
RPC: Initial implementation of a multiple-argument dispatch This code uses some kludges (discussed with Ian previously and hopefully well documented here) to get a type-identifier for each type in a const context. It then defines a macro to declare a type-erased versions of a concrete implementation functions, and register those implementations to be called later. We will probably want to tweak a bunch of this code as we move ahead.
2023-04-03 15:23:55 +01:00
"inventory",
"once_cell",
"paste",
Start on a lower-level tor-rpccmd crate. This crate will hold the backend pieces of RPC interaction that different parts of Arti get to implement.
2023-03-31 16:57:05 +01:00
"serde",
rpc: Make invoke return a Result of erased_serde::Serialize This will let the actual RPC functions return any Result type that we can serialize.
2023-04-04 15:18:06 +01:00
"serde_json",
rpcbase: Use correct error codes, and add tests. Well, mostly correct. Our current serde implementation doesn't tell us much about what went wrong with the object, so we can't tell why we couldn't convert it into a Request. Also, our output for the data field is not as the spec says: we should bring them into conformance. Part of #825.
2023-04-12 18:32:15 +01:00
"serde_repr",
Start on a lower-level tor-rpccmd crate. This crate will hold the backend pieces of RPC interaction that different parts of Arti get to implement.
2023-03-31 16:57:05 +01:00
"thiserror",
rpcbase: Use with_fn.
2023-04-18 20:52:14 +01:00
"tor-async-utils",
rpc: Add an RpcError type. This could have been a trait instead, but I don't know whether that's smart or not. There is a lot of opportunity for refactoring here.
2023-04-04 16:05:35 +01:00
"tor-error",
Start on a lower-level tor-rpccmd crate. This crate will hold the backend pieces of RPC interaction that different parts of Arti get to implement.
2023-03-31 16:57:05 +01:00
"typetag",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "tor-rtcompat"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.9.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"async-io",
"async-native-tls",
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
"async-rustls",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"async-std",
"async-trait",
"async_executors",
Replace manual Clone impl with educe in tor-rtcompat
2022-03-02 15:13:48 +00:00
"educe",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"futures",
"native-tls",
"pin-project",
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
"rustls",
`TaskSchedule`: give error on `sleep*()` if last handle is dropped This fixes an busy-loop. When the last `TaskHandle` on a `TaskSchedule` is dropped, the schedule is permanently canceled: whatever operation it was scheduling should no longer be performed. But our code was broken: the `sleep()` and `sleep_until_wallclock()` functions don't verify whether the handles are dropped or not. This breakage caused an CPU-eating busy-loop in `sleep_until_wallclock`. With this patch, we now return a `Result<(), SleepError>` from these functions. Fixes #572.
2022-09-07 14:22:38 +01:00
"thiserror",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tokio",
"tokio-util",
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
"x509-signature",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "tor-rtmock"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.8.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
tor-rtmock: Provide MockRuntime
2023-07-05 10:29:15 +01:00
"amplify",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"async-trait",
tor-rtmock: Use derive-adhoc for composite runtimes
2023-07-06 15:46:35 +01:00
"derive-adhoc",
tor-rtmock: Provide MockExecutor
2023-07-03 13:11:18 +01:00
"educe",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"futures",
"futures-await-test",
Use parse_rfc3339() in the tor-rtmock crate
2022-12-16 21:07:49 +00:00
"humantime 2.1.0",
tor-rtmock: Provide MockExecutor
2023-07-03 13:11:18 +01:00
"itertools 0.11.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"pin-project",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"rand 0.8.5",
tor-rtmock: Provide MockExecutor
2023-07-03 13:11:18 +01:00
"slotmap",
tor-rtmock: MockExecutor: Configurable scheduling policy
2023-07-05 15:57:59 +01:00
"strum",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"thiserror",
Use testing_rng() in tests throughout our crates. This only affects uses of thread_rng(), and affects them all more or less indiscriminately. One test does not work with ARTI_TEST_PRNG=deterministic; the next commit will fix it.
2022-06-02 18:31:43 +01:00
"tor-basic-utils",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"tor-rtcompat",
Replace all println/eprintln calls outside of arti CLI with trace.
2021-11-04 15:04:59 +00:00
"tracing",
tor-rtmock: Unit tests for MockExecutor
2023-07-04 11:36:26 +01:00
"tracing-test",
tor-rtmock: MockRuntime: provide test_with_various In both fallible and infallible variants, for convenience.
2023-07-05 15:59:48 +01:00
"void",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "tor-socksproto"
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
version = "0.7.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Fuzzer code for socks client implementation.
2022-09-27 22:16:14 +01:00
"arbitrary",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"caret",
"hex-literal",
Make sure that socks4 auth doesn't have any 0 bytes. Try to do it in constant time, to avoid even the smell of side-channel attacks.
2022-09-30 13:09:26 +01:00
"subtle",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"thiserror",
"tor-bytes",
tor-socksproto: Implement HasKind (This error isn't yet wrapped in TorError, but it will be eventually when we implement socks proxy and PT support.)
2022-02-09 16:36:21 +00:00
"tor-error",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "tor-units"
Bump versions on crates with nonfunctional changes These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ```
2023-06-30 13:30:55 +01:00
version = "0.6.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"derive_more",
update misc/Cargo.lock
2021-09-12 09:28:00 +01:00
"float-cmp",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"thiserror",
]
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
[[package]]
name = "tower-service"
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
version = "0.3.2"
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
checksum = "b6bc1c9ce2b5135ac7f93c72918fc37feb872bdc6a5533a8b85eb4b86bfdae52"
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "tracing"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.1.37"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "8ce8c33a8d48bd45d624a6e523445fd21ec13d3653cd51f681abf67418f54eb8"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"pin-project-lite",
"tracing-attributes",
"tracing-core",
]
Tracing configuration for logfiles, per-target filters Previously we could only configure one global tracing filter that applied to stdout and journald. There was no support for log files, either. This patch fixes both issues, by substantially revising the configuration format: There are now separate filters for each log file, for journald, and for the console log. Because we want to allow multiple logfiles, they have to go into an array in the configuration. The configuration logic has grown a bit complicated in its types, since the tracing_subscriber crate would prefer to have the complete structure of tracing Layers known statically. That's fine when you know how many you have, and which kinds there will be, but for the runtime-configuration case we need to mess around with `Box<dyn Layer ...>`. I also had to switch from tracing_subscriber's EnvFilter to its Targets filter. It seems "EnvFilter" can only be applied as a Layer in itself, and won't work as a Filter on an individual Layer. Closes #166. Closes #170.
2022-01-07 15:52:43 +00:00
[[package]]
name = "tracing-appender"
Run cargo-update in preparation for Arti 0.2.0 (Doing this a few days ahead of time to give updated code time to get testing)
2022-03-29 18:22:28 +01:00
version = "0.2.2"
Tracing configuration for logfiles, per-target filters Previously we could only configure one global tracing filter that applied to stdout and journald. There was no support for log files, either. This patch fixes both issues, by substantially revising the configuration format: There are now separate filters for each log file, for journald, and for the console log. Because we want to allow multiple logfiles, they have to go into an array in the configuration. The configuration logic has grown a bit complicated in its types, since the tracing_subscriber crate would prefer to have the complete structure of tracing Layers known statically. That's fine when you know how many you have, and which kinds there will be, but for the runtime-configuration case we need to mess around with `Box<dyn Layer ...>`. I also had to switch from tracing_subscriber's EnvFilter to its Targets filter. It seems "EnvFilter" can only be applied as a Layer in itself, and won't work as a Filter on an individual Layer. Closes #166. Closes #170.
2022-01-07 15:52:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo-update in preparation for Arti 0.2.0 (Doing this a few days ahead of time to give updated code time to get testing)
2022-03-29 18:22:28 +01:00
checksum = "09d48f71a791638519505cefafe162606f706c25592e4bde4d97600c0195312e"
Tracing configuration for logfiles, per-target filters Previously we could only configure one global tracing filter that applied to stdout and journald. There was no support for log files, either. This patch fixes both issues, by substantially revising the configuration format: There are now separate filters for each log file, for journald, and for the console log. Because we want to allow multiple logfiles, they have to go into an array in the configuration. The configuration logic has grown a bit complicated in its types, since the tracing_subscriber crate would prefer to have the complete structure of tracing Layers known statically. That's fine when you know how many you have, and which kinds there will be, but for the runtime-configuration case we need to mess around with `Box<dyn Layer ...>`. I also had to switch from tracing_subscriber's EnvFilter to its Targets filter. It seems "EnvFilter" can only be applied as a Layer in itself, and won't work as a Filter on an individual Layer. Closes #166. Closes #170.
2022-01-07 15:52:43 +00:00
dependencies = [
"crossbeam-channel",
"time",
"tracing-subscriber",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "tracing-attributes"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.1.26"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "5f4f31f56159e98206da9efd823404b79b6ef3143b4a7ab76e67b1751b25a4ab"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "tracing-core"
Run "cargo update".
2023-05-22 12:47:20 +01:00
version = "0.1.31"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2023-05-22 12:47:20 +01:00
checksum = "0955b8137a1df6f1a2e9a37d8a6656291ff0297c1a97c24e0d8425fe2312f79a"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
"once_cell",
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
"valuable",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
update misc/Cargo.lock
2021-09-12 09:28:00 +01:00
[[package]]
name = "tracing-journald"
Upgrade tracing-journald to 0.3.0
2022-04-25 21:11:46 +01:00
version = "0.3.0"
update misc/Cargo.lock
2021-09-12 09:28:00 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade tracing-journald to 0.3.0
2022-04-25 21:11:46 +01:00
checksum = "ba316a74e8fc3c3896a850dba2375928a9fa171b085ecddfc7c054d39970f3fd"
update misc/Cargo.lock
2021-09-12 09:28:00 +01:00
dependencies = [
Run "cargo update".
2022-01-11 14:27:22 +00:00
"libc",
update misc/Cargo.lock
2021-09-12 09:28:00 +01:00
"tracing-core",
Remove usage of tracing-test 0.1 It requires tracing-subscriber 0.2, which is a lower version than we want, and which causes trouble with our minimal-versions CI test. There is a pending issue to fix this; we can reinstate tracing-test once it is merged: https://github.com/dbrgn/tracing-test/pull/11
2021-11-11 15:58:25 +00:00
"tracing-subscriber",
update misc/Cargo.lock
2021-09-12 09:28:00 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "tracing-log"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
version = "0.1.3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for a release... next week?
2022-05-04 19:17:11 +01:00
checksum = "78ddad33d2d10b1ed7eb9d1f518a5674713876e97e5bb9b7345a7984fbb4f922"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"lazy_static",
"log",
"tracing-core",
]
[[package]]
name = "tracing-subscriber"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
version = "0.3.17"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
checksum = "30a651bc37f915e81f087d86e62a18eec5f79550c7faff886f7090b4ea757c77"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Remove usage of tracing-test 0.1 It requires tracing-subscriber 0.2, which is a lower version than we want, and which causes trouble with our minimal-versions CI test. There is a pending issue to fix this; we can reinstate tracing-test once it is merged: https://github.com/dbrgn/tracing-test/pull/11
2021-11-11 15:58:25 +00:00
"matchers",
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
"nu-ansi-term",
cargo update This fixes a complaint from cargo audit about https://rustsec.org/advisories/RUSTSEC-2022-0032 in openssl.
2022-07-05 17:52:28 +01:00
"once_cell",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"regex",
"sharded-slab",
"smallvec",
"thread_local",
"tracing",
"tracing-core",
"tracing-log",
]
Add a few tests to tor-config.
2021-12-08 00:52:49 +00:00
[[package]]
name = "tracing-test"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
version = "0.2.4"
Add a few tests to tor-config.
2021-12-08 00:52:49 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
checksum = "3a2c0ff408fe918a94c428a3f2ad04e4afd5c95bbc08fcf868eff750c15728a4"
Add a few tests to tor-config.
2021-12-08 00:52:49 +00:00
dependencies = [
"lazy_static",
"tracing-core",
"tracing-subscriber",
"tracing-test-macro",
]
[[package]]
name = "tracing-test-macro"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
version = "0.2.4"
Add a few tests to tor-config.
2021-12-08 00:52:49 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
checksum = "258bc1c4f8e2e73a977812ab339d503e6feeb92700f6d07a6de4d321522d5c08"
Add a few tests to tor-config.
2021-12-08 00:52:49 +00:00
dependencies = [
"lazy_static",
"quote",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
Add a few tests to tor-config.
2021-12-08 00:52:49 +00:00
]
actually add DNS support
2022-03-06 19:44:50 +00:00
[[package]]
name = "trust-dns-proto"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
version = "0.22.0"
actually add DNS support
2022-03-06 19:44:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
checksum = "4f7f83d1e4a0e4358ac54c5c3681e5d7da5efc5a7a632c90bb6d6669ddd9bc26"
actually add DNS support
2022-03-06 19:44:50 +00:00
dependencies = [
"async-trait",
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
actually add DNS support
2022-03-06 19:44:50 +00:00
"data-encoding",
"enum-as-inner",
"futures-channel",
"futures-io",
"futures-util",
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
"idna 0.2.3",
actually add DNS support
2022-03-06 19:44:50 +00:00
"ipnet",
"lazy_static",
"rand 0.8.5",
"smallvec",
"thiserror",
"tinyvec",
"tokio",
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
"tracing",
actually add DNS support
2022-03-06 19:44:50 +00:00
"url",
]
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
[[package]]
name = "try-lock"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
version = "0.2.4"
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
checksum = "3528ecfd12c466c6f163363caf2d02a71161dd5e1cc6ae7b34207ea2d42d81ed"
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
tor-netdir: Use typed-index-collections for router status index
2023-02-01 19:14:07 +00:00
[[package]]
name = "typed-index-collections"
version = "3.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "183496e014253d15abbe6235677b1392dba2d40524c88938991226baa38ac7c4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "typenum"
Upgrade to latest rsa crate.
2023-01-19 20:22:18 +00:00
version = "1.16.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade to latest rsa crate.
2023-01-19 20:22:18 +00:00
checksum = "497961ef93d974e23eb6f433eb5fe1b7930b659f06d12dec6fc44a8f554c0bba"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
[[package]]
name = "typetag"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
version = "0.2.8"
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
checksum = "6a6898cc6f6a32698cc3e14d5632a14d2b23ed9f7b11e6b8e05ce685990acc22"
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
dependencies = [
"erased-serde",
"inventory",
"once_cell",
"serde",
"typetag-impl",
]
[[package]]
name = "typetag-impl"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
version = "0.2.8"
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release next week
2023-04-28 22:09:03 +01:00
checksum = "2c3e1c30cedd24fc597f7d37a721efdbdc2b1acae012c1ef1218f4c7c2c0f3e7"
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
rpc: Implement json message types for serde.
2023-03-29 16:20:46 +01:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "unicode-bidi"
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
version = "0.3.13"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
checksum = "92888ba5573ff080736b3648696b70cafad7d250551175acbaa4e0385b3e1460"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
Run "cargo update" in preparation for the next release.
2022-05-24 20:08:01 +01:00
[[package]]
name = "unicode-ident"
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
version = "1.0.9"
Run "cargo update" in preparation for the next release.
2022-05-24 20:08:01 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Thursday release.
2023-05-30 15:37:24 +01:00
checksum = "b15811caf2415fb889178633e7724bad2509101cde276048e013b9def5e51fa0"
Run "cargo update" in preparation for the next release.
2022-05-24 20:08:01 +01:00
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "unicode-normalization"
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
version = "0.1.22"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
checksum = "5c5713f0fc4b5db668a2ac63cdb7bb4469d8c9fed047b1d0292cc7b0ce2ba921"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"tinyvec",
]
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
[[package]]
name = "untrusted"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "55cd1f4b4e96b46aeb8d4855db4a7a9bd96eeeb5c6a1ab54593328761642ce2f"
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
[[package]]
name = "untrusted"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a156c684c91ea7d62626509bce3cb4e1d9ed5c4d978f7b4352658f96a4c26b4a"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "url"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "2.4.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "50bff7831e19200a85b17131d085c25d7811bc4e186efdaf54bbd132994a88cb"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"form_urlencoded",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"idna 0.4.0",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"percent-encoding",
]
fs-mistrust: Add code to make a self-named group "trusted". This required a bit of poking through the `users` crate, to mess with the user and group dbs. The original goal was to "trust the group with the same name as us", but it turned into a bit of a production, since: * We want to take our own name from $USER, assuming that matches our uid. (Otherwise we want to ask getpwuid_r().) * We only want to trust the group if we are actually a member of that group. * We want to cache this information. * We want to test this code.
2022-04-27 20:20:56 +01:00
[[package]]
name = "users"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "24cc0f6d6f267b73e5a2cadf007ba8f9bc39c6a6f9666f8cf25ea809a153b032"
dependencies = [
"libc",
"log",
]
Run "cargo upgrade" in preparation for 0.1.0. (It's good to do this a couple of days in advance in case it turns up any bugs. That's how we caught the panic bug in simple_asn1 0.6.0)
2022-02-25 16:32:09 +00:00
[[package]]
name = "valuable"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "830b7e5d4d90034032940e4ace0d9a9a057e7a45cd94e6c007832e39edb82f6d"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "value-bag"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "1.4.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "d92ccd67fb88503048c01b59152a04effd0782d035a83a6d256ce6085f08f4a3"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "vcpkg"
version = "0.2.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "accd4ea62f7bb7a82fe23066fb0957d48ef677f6eeb8215f372f52e48bb32426"
[[package]]
name = "version_check"
Run "cargo update".
2022-01-11 14:27:22 +00:00
version = "0.9.4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2022-01-11 14:27:22 +00:00
checksum = "49874b5167b65d7193b8aba1567f5c7d93d001cafc34600cee003eda787e483f"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
tor-netdoc: Conditionally expose document fields. This commit uses the `visibility` and `visible` crates to conditionally make certain structs and their fields public (respectively). This is incredibly dangerous to use for anything besides testing, and I've tried to write the documentation for the feature accordingly.
2022-03-31 14:20:21 +01:00
[[package]]
name = "visibility"
version = "0.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8881d5cc0ae34e3db2f1de5af81e5117a420d2f937506c2dc20d6f4cfb069051"
dependencies = [
"proc-macro2",
"quote",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
tor-netdoc: Conditionally expose document fields. This commit uses the `visibility` and `visible` crates to conditionally make certain structs and their fields public (respectively). This is incredibly dangerous to use for anything besides testing, and I've tried to write the documentation for the feature accordingly.
2022-03-31 14:20:21 +01:00
]
[[package]]
name = "visible"
version = "0.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a044005fd5c0fc1ebd79c622e5606431c6b879a6a19acafb754be9926a2de73e"
dependencies = [
"quote",
Upgrade dependency to latest async-native-tls.
2023-03-30 13:32:18 +01:00
"syn 1.0.109",
tor-netdoc: Conditionally expose document fields. This commit uses the `visibility` and `visible` crates to conditionally make certain structs and their fields public (respectively). This is incredibly dangerous to use for anything besides testing, and I've tried to write the documentation for the feature accordingly.
2022-03-31 14:20:21 +01:00
]
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
[[package]]
name = "void"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6a02e4885ed3bc0f2de90ea6dd45ebcbb66dacffe03547fadbb0eeae2770887d"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "waker-fn"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9d5b2c62b4012a3e1eca5a7e077d13b3bf498c4073e33ccd58626607748ceeca"
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
[[package]]
name = "walkdir"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "2.3.3"
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "36df944cda56c7d8d8b7496af378e6b16de9284591917d307c9b4d313c44e698"
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
dependencies = [
"same-file",
"winapi-util",
]
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
[[package]]
name = "want"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.3.1"
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "bfa7760aed19e106de2c7c0b581b509f2f25d3dacaf737cb82ac61bc6d760b0e"
tor-client/examples: add `hyper` example The new `hyper` tor-client example demonstrates integrating arti with the popular Rust `hyper` HTTP library by implementing a custom Hyper "connector" (a type that can initiate connections to HTTP servers) that proxies said connections via the Tor network.
2021-10-19 17:26:55 +01:00
dependencies = [
"try-lock",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "wasi"
version = "0.9.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cccddf32554fecc6acb585f82a32a72e28b48f8c4c1883ddfeeeaa96f7d8e519"
Run "cargo update" in preparation for monday's release.
2022-01-28 13:38:54 +00:00
[[package]]
name = "wasi"
version = "0.11.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9c8d87e72b64a3b4db28d11ce29237c246188f4f51057d65a7eab63b7987e423"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "wasm-bindgen"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.2.87"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "7706a72ab36d8cb1f80ffbf0e071533974a60d0a308d01a5d0375bf60499a342"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"wasm-bindgen-macro",
]
[[package]]
name = "wasm-bindgen-backend"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.2.87"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "5ef2b6d3c510e9625e5fe6f509ab07d66a760f0885d858736483c32ed7809abd"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"bumpalo",
"log",
Run "cargo update" in preparation for next week's release.
2022-07-27 14:27:30 +01:00
"once_cell",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-futures"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.4.37"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "c02dbc21516f9f1f04f187958890d7e6026df8d16540b7ad9492bc34a67cea03"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Temporarily replace generational-arena with a fake version. This fake version is completely silly, but it will do the job until we figure out our MPL2 concerns.
2023-05-03 20:13:19 +01:00
"cfg-if",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"js-sys",
"wasm-bindgen",
"web-sys",
]
[[package]]
name = "wasm-bindgen-macro"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.2.87"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "dee495e55982a3bd48105a7b947fd2a9b4a8ae3010041b9e0faab3f9cd028f1d"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"quote",
"wasm-bindgen-macro-support",
]
[[package]]
name = "wasm-bindgen-macro-support"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.2.87"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "54681b18a46765f095758388f2d0cf16eb8d4169b639ab575a8f5693af210c7b"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"wasm-bindgen-backend",
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-shared"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.2.87"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "ca6ad05a4870b2bf5fe995117d3728437bd27d7cd5f06f13c17443ef369775a1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "weak-table"
Run "cargo update".
2022-01-11 14:27:22 +00:00
version = "0.3.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update".
2022-01-11 14:27:22 +00:00
checksum = "323f4da9523e9a669e1eaf9c6e763892769b1d38c623913647bfdc1532fe4549"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "web-sys"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.3.64"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "9b85cbef8c220a6abc02aefd892dfc0fc23afb1c6a426316ec33253a3877249b"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"js-sys",
"wasm-bindgen",
]
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
[[package]]
name = "webpki"
version = "0.22.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f095d78192e208183081cc07bc5515ef55216397af48b873e5edcd72637fa1bd"
dependencies = [
"ring",
"untrusted 0.7.1",
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
]
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
[[package]]
name = "wide"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.7.10"
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "40018623e2dba2602a9790faba8d33f2ebdebf4b86561b83928db735f8784728"
Upgrade statrs in preparation for release.
2022-08-30 16:17:01 +01:00
dependencies = [
"bytemuck",
"safe_arch",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "winapi"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
dependencies = [
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
[[package]]
name = "winapi-util"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
dependencies = [
update to v5.0.0
2022-08-12 19:50:08 +01:00
"winapi",
Reload configuration when our configuration files change. Closes #270
2022-02-01 18:30:31 +00:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
[[package]]
name = "windows"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "0.48.0"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "e686886bc078bc1b0b600cac0147aadb815089b6e4da64016cbd754b6342700f"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
dependencies = [
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"windows-targets 0.48.1",
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
]
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
[[package]]
name = "windows-sys"
version = "0.42.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5a3e1820f08b8513f676f7ab6c1f99ff312fb97b553d30ff4dd86f9f15728aa7"
dependencies = [
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
"windows_aarch64_gnullvm 0.42.2",
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
"windows_aarch64_msvc 0.42.2",
"windows_i686_gnu 0.42.2",
"windows_i686_msvc 0.42.2",
"windows_x86_64_gnu 0.42.2",
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
"windows_x86_64_gnullvm 0.42.2",
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
"windows_x86_64_msvc 0.42.2",
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
]
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
[[package]]
name = "windows-sys"
version = "0.45.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "75283be5efb2831d37ea142365f009c02ec203cd29a3ebecbc093d52315b66d0"
dependencies = [
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
"windows-targets 0.42.2",
]
[[package]]
name = "windows-sys"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "677d2418bec65e3338edb076e806bc1ec15693c5d0104683f2efe857f61056a9"
dependencies = [
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"windows-targets 0.48.1",
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
]
[[package]]
name = "windows-targets"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.42.2"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "8e5180c00cd44c9b1c88adb3693291f1cd93605ded80c250a75d472756b4d071"
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
dependencies = [
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
"windows_aarch64_gnullvm 0.42.2",
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
"windows_aarch64_msvc 0.42.2",
"windows_i686_gnu 0.42.2",
"windows_i686_msvc 0.42.2",
"windows_x86_64_gnu 0.42.2",
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
"windows_x86_64_gnullvm 0.42.2",
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
"windows_x86_64_msvc 0.42.2",
Run "cargo update" in preparation for the release in 2 weeks.
2023-02-17 19:22:57 +00:00
]
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
[[package]]
name = "windows-targets"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.48.1"
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "05d4b17490f70499f20b9e791dcf6a299785ce8af4d709018206dc5b4953e95f"
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
dependencies = [
"windows_aarch64_gnullvm 0.48.0",
"windows_aarch64_msvc 0.48.0",
"windows_i686_gnu 0.48.0",
"windows_i686_msvc 0.48.0",
"windows_x86_64_gnu 0.48.0",
"windows_x86_64_gnullvm 0.48.0",
"windows_x86_64_msvc 0.48.0",
]
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
[[package]]
name = "windows_aarch64_gnullvm"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "597a5118570b68bc08d8d59125332c54f1ba9d9adeedeef5b99b02ba2b0698f8"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
[[package]]
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
name = "windows_aarch64_gnullvm"
version = "0.48.0"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
checksum = "91ae572e1b79dba883e0d315474df7305d12f569b400fcf90581b06062f7e1bc"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
[[package]]
name = "windows_aarch64_msvc"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e08e8864a60f06ef0d0ff4ba04124db8b0fb3be5776a5cd47641e942e58c4d43"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
[[package]]
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
name = "windows_aarch64_msvc"
version = "0.48.0"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
checksum = "b2ef27e0d7bdfcfc7b868b317c1d32c641a6fe4629c171b8928c7b08d98d7cf3"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
[[package]]
name = "windows_i686_gnu"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c61d927d8da41da96a81f029489353e68739737d3beca43145c8afec9a31a84f"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
[[package]]
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
name = "windows_i686_gnu"
version = "0.48.0"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
checksum = "622a1962a7db830d6fd0a69683c80a18fda201879f0f447f065a3b7467daa241"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
[[package]]
name = "windows_i686_msvc"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "44d840b6ec649f480a41c8d80f9c65108b92d89345dd94027bfe06ac444d1060"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
[[package]]
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
name = "windows_i686_msvc"
version = "0.48.0"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
checksum = "4542c6e364ce21bf45d69fdd2a8e455fa38d316158cfd43b3ac1c5b1b19f8e00"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
[[package]]
name = "windows_x86_64_gnu"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.42.2"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "8de912b8b8feb55c064867cf047dda097f92d51efad5b491dfb98f6bbb70cb36"
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
[[package]]
name = "windows_x86_64_gnu"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ca2b8a661f7628cbd23440e50b05d705db3686f894fc9580820623656af974b1"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
[[package]]
name = "windows_x86_64_gnullvm"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "26d41b46a36d453748aedef1486d5c7a85db22e56aff34643984ea85514e94a3"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
[[package]]
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
name = "windows_x86_64_gnullvm"
version = "0.48.0"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
checksum = "7896dbc1f41e08872e9d5e8f8baa8fdd2677f29468c4e156210174edc7f7b953"
Upgrade dependencies in preparation for upcoming release
2022-09-30 19:07:25 +01:00
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
[[package]]
name = "windows_x86_64_msvc"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "0.42.2"
Upgrade dependencies in preparation for upcoming release(s)
2022-10-28 19:51:01 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "9aec5da331524158c6d1a4ac0ab1541149c0b9505fde06423b02f5ef0106b9f0"
Update our secmem_proc dependency to 0.3.0 (This wasn't possible before we updated our MSRV to 1.65.) Closes #664.
2023-04-13 12:41:02 +01:00
[[package]]
name = "windows_x86_64_msvc"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1a515f5799fe4961cb532f983ce2b23082366b898e52ffbce459c86f67c8378a"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
[[package]]
name = "winnow"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
version = "0.4.7"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
checksum = "ca0ace3845f0d96209f0375e6d367e3eb87eb65d27d445bdc9f1843a26f39448"
Run cargo update in preparation for Wednesday Release
2023-02-27 12:47:11 +00:00
dependencies = [
"memchr",
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "x25519-dalek"
Back down x25519-dalek to 2.0.0-pre.1 from 2.0.0-rc.2 ========================= Notes from nickm: (This differs from pinkforest's original MR: It removes the Cargo.lock changes and the version bump on tor-llcrypto.) Minimal Cargo.lock changes from downgrade. (These are exactly those changes generated by running "build" and "test".) There are several reasons to do this: * It's best to bump all of our dalek dependencies at once to rc.3 or later, rather than the piecemeal approach we've been stuck with so far. * We don't want to do this bump right now, since there are some tricky questions about clamping we need to figure out (see #808), and we need to make sure we get them right, and we're in a distracted this week. * We _do_ need to move away from 2.0.0-rc.2 right now, since it was causing a failure in `cargo install arti`, and then it got yanked. Thanks to pinkforest for helping us out here and explaining all of this! Fixes #926. Commit-edited-by: Nick Mathewson <nickm@torproject.org>
2023-06-27 01:45:36 +01:00
version = "2.0.0-pre.1"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Back down x25519-dalek to 2.0.0-pre.1 from 2.0.0-rc.2 ========================= Notes from nickm: (This differs from pinkforest's original MR: It removes the Cargo.lock changes and the version bump on tor-llcrypto.) Minimal Cargo.lock changes from downgrade. (These are exactly those changes generated by running "build" and "test".) There are several reasons to do this: * It's best to bump all of our dalek dependencies at once to rc.3 or later, rather than the piecemeal approach we've been stuck with so far. * We don't want to do this bump right now, since there are some tricky questions about clamping we need to figure out (see #808), and we need to make sure we get them right, and we're in a distracted this week. * We _do_ need to move away from 2.0.0-rc.2 right now, since it was causing a failure in `cargo install arti`, and then it got yanked. Thanks to pinkforest for helping us out here and explaining all of this! Fixes #926. Commit-edited-by: Nick Mathewson <nickm@torproject.org>
2023-06-27 01:45:36 +01:00
checksum = "e5da623d8af10a62342bcbbb230e33e58a63255a58012f8653c578e54bab48df"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
Back down x25519-dalek to 2.0.0-pre.1 from 2.0.0-rc.2 ========================= Notes from nickm: (This differs from pinkforest's original MR: It removes the Cargo.lock changes and the version bump on tor-llcrypto.) Minimal Cargo.lock changes from downgrade. (These are exactly those changes generated by running "build" and "test".) There are several reasons to do this: * It's best to bump all of our dalek dependencies at once to rc.3 or later, rather than the piecemeal approach we've been stuck with so far. * We don't want to do this bump right now, since there are some tricky questions about clamping we need to figure out (see #808), and we need to make sure we get them right, and we're in a distracted this week. * We _do_ need to move away from 2.0.0-rc.2 right now, since it was causing a failure in `cargo install arti`, and then it got yanked. Thanks to pinkforest for helping us out here and explaining all of this! Fixes #926. Commit-edited-by: Nick Mathewson <nickm@torproject.org>
2023-06-27 01:45:36 +01:00
"curve25519-dalek",
Run cargo update in preparation for upcoming release.
2022-09-30 19:20:15 +01:00
"rand_core 0.6.4",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
"zeroize",
]
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
[[package]]
name = "x509-signature"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9fb2bc2a902d992cd5f471ee3ab0ffd6603047a4207384562755b9d6de977518"
dependencies = [
"ring",
arti-hyper: Provide TLS connector and make space for TLS stream Add tls_conn field to ArtiHttpConnector (and argument to constructor). Introduce MaybeHttpsStream and use it in ArtiHttpConnection. Have the example program pass the native TLS connector. Currently the TLS connector and the HTTPS variant are not used, but this commit is very noisy and fomrulaic, so I have split out the code to use them into a separate commit for easier preparation and review.
2022-02-25 11:24:19 +00:00
"untrusted 0.7.1",
tor-rtcompat: Add support for rustls. This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
2022-01-21 14:28:11 +00:00
]
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
[[package]]
name = "xz2"
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
version = "0.1.7"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release on Friday
2022-06-21 13:54:12 +01:00
checksum = "388c44dc09d76f1536602ead6d325eb532f5c122f17782bd57fb47baeeb767e2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"lzma-sys",
]
[[package]]
name = "zeroize"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
version = "1.6.0"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update in preparation for release tomorrow.
2023-03-30 19:49:23 +01:00
checksum = "2a0956f1ba7c7909bfb66c2e9e4124ab6f6482560f6628b5aaeba39207c9aad9"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"zeroize_derive",
]
[[package]]
name = "zeroize_derive"
Run cargo-update to move away from yanked versions of "windows" (cargo-audit is complaining about these and breaking CI)
2023-03-31 14:40:12 +01:00
version = "1.4.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo-update to move away from yanked versions of "windows" (cargo-audit is complaining about these and breaking CI)
2023-03-31 14:40:12 +01:00
checksum = "ce36e65b0d2999d2aafac989fb249189a141aee1f53c612c1f37d72631959f69"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"proc-macro2",
"quote",
Run "cargo update" in preparation for Friday release.
2023-06-29 13:30:51 +01:00
"syn 2.0.22",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]
[[package]]
name = "zstd"
Upgrade async-compression dependency to 0.4.0.
2023-05-22 12:52:18 +01:00
version = "0.12.3+zstd.1.5.2"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade async-compression dependency to 0.4.0.
2023-05-22 12:52:18 +01:00
checksum = "76eea132fb024e0e13fd9c2f5d5d595d8a967aa72382ac2f9d39fcc95afd0806"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"zstd-safe",
]
[[package]]
name = "zstd-safe"
Upgrade async-compression dependency to 0.4.0.
2023-05-22 12:52:18 +01:00
version = "6.0.5+zstd.1.5.4"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade async-compression dependency to 0.4.0.
2023-05-22 12:52:18 +01:00
checksum = "d56d9e60b4b1758206c238a10165fbcae3ca37b01744e394c463463f6529d23b"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"libc",
"zstd-sys",
]
[[package]]
name = "zstd-sys"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
version = "2.0.8+zstd.1.5.5"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Run cargo update The lockfile on main seems to be broken. I skim-eyeballed the diff, which is entirely autogenerated.
2023-04-13 15:44:02 +01:00
checksum = "5556e6ee25d32df2586c098bbfa278803692a20d0ab9565e049480d52707ec8c"
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
dependencies = [
"cc",
"libc",
Run cargo update in preparation for release tomorrow
2023-01-31 20:37:48 +00:00
"pkg-config",
make arti availlable as build artifact and make builds reproducible sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
2021-08-25 16:16:49 +01:00
]