summaryrefslogtreecommitdiff
path: root/Cargo.lock
Commit message (Collapse)AuthorAgeFilesLines
...
* Upgrade to latest async-broadcastNick Mathewson2023-01-201-2/+2
| | | | | (We don't yet use the code that uses it, but we might as well have our unused code be up-to-date.)
* upgrade to latest serial_testNick Mathewson2023-01-201-31/+6
|
* Complete our migration to base64ct.Nick Mathewson2023-01-201-5/+5
| | | | | | | | | 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.
* Upgrade to latest rlimit crate.Nick Mathewson2023-01-191-4/+4
|
* Merge branch 'onion-api-client-toplevel' into 'main'eta2023-01-171-0/+1
|\ | | | | | | | | Make a top-level API for connecting to onion services. See merge request tpo/core/arti!971
| * Make a top-level API for connecting to onion services.Nick Mathewson2023-01-121-0/+1
| | | | | | | | Fortunately, it adds very little to the arti-client API surface.
* | Bump Cargo.lock to ed25519 1.5.3 to fix CI.Nick Mathewson2023-01-161-2/+2
|/ | | | ed25519 1.5.2 has been yanked.
* Sketch APIs for the onion service directory ring.Nick Mathewson2023-01-111-0/+1
| | | | | | | | | 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.
* Upgrade to latest tokio, for security fix.Nick Mathewson2023-01-091-3/+3
| | | | | | | On 1.22, cargo audit is complaining about RUSTSEC-2023-0001. We aren't affected, since we don't use windows named pipes (yet), but let's make cargo audit happier.
* Merge branch 'arti-hyper-fixing-715' into 'main'eta2023-01-091-0/+16
|\ | | | | | | | | | | | | Temporary fix for #715 and #569 Closes #715 See merge request tpo/core/arti!958
| * Updated Cargo.lockMichael van Straten2023-01-061-0/+16
| |
* | Merge branch 'onion-api-v0.2' into 'main'Nick Mathewson2023-01-061-0/+12
|\ \ | | | | | | | | | | | | Onion service APIs, part 1. See merge request tpo/core/arti!959
| * | Sketch out new required APIs in tor-cellNick Mathewson2023-01-061-0/+1
| | |
| * | netdoc: Outline some basic types for encoding HsDescs.Nick Mathewson2023-01-061-0/+2
| | |
| * | Create a new tor-hscrypto crate.Nick Mathewson2023-01-061-0/+9
| | | | | | | | | | | | | | | | | | 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.
* | | tor-proto: When relay IDs mismatch, the IDs are sensitive in errorsIan Jackson2023-01-061-0/+1
|/ /
* / Use parse_rfc3339() in the tor-rtmock crateNeel Chauhan2022-12-161-0/+1
|/
* Tackling issue #663 (Use humantime in tests)coral2022-12-121-0/+3
|
* tor-config: Update to shellexpand 3.xIan Jackson2022-12-061-2/+2
| | | | | | | | | | | | | | | | | | | | | This is the new upstream version (published by me, recently). It has the same MSRV and one breaking change: The caller who specifies a home dir function for substituting into strings, must now supply a string, not Path. Previously shellexpand would allow the caller to supply non-unicode data, and then simply not substitute it. That was an infelicity in the shellexpand API. Now this infelicity is pushed into our code. The overall behaviour of Arti hasn't changed as a result. And it seems reasonable to me. shellexpand 3.x also has a module for expanding Paths instead, in response to requests for this filed as upstream tickets. We *could* use that but I am not sanguine about that approach: the Pathness would spread throughout much of our config and file handling code. I think we should at the very least postpone trying to work with invalid-unicode-paths as long as we can.
* Bump the minor version of every crate.Nick Mathewson2022-11-301-37/+37
| | | | | We made this job easy this time around: by incrementing our MSRV, we have forced ourselves to do at least a minor bump everywhere.
* ptmgr: Use anonymize_home when displaying paths in errorsNick Mathewson2022-11-291-0/+1
|
* Merge branch 'more-linkspec-tests' into 'main'Nick Mathewson2022-11-291-0/+1
|\ | | | | | | | | Add tests for a bunch of code in tor-linkspec See merge request tpo/core/arti!867
| * linkspec: Add some tests for ChannelMethodNick Mathewson2022-11-281-0/+1
| |
* | Merge branch 'ptmgr-cleanup' into 'main'Nick Mathewson2022-11-291-1/+1
|\ \ | | | | | | | | | | | | | | | | | | Post-merge cleanups for PtMgr Closes #667 and #659 See merge request tpo/core/arti!893
| * | PtMgr: Use a persistent state directory for PT state.Nick Mathewson2022-11-281-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This makes a `pt_state` directory inside .local/share/arti (or the local equivalent), right next to our existing `state` dir. Ideally we would use a separate directory for each PT, but we have a very fuzzy "what is a specific PT" notion. Closes #667
| * | ptmgr: Mark PtMessage and next_message as experimental-api.Nick Mathewson2022-11-281-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | Switch from sha-1 back to sha1.Nick Mathewson2022-11-291-4/+4
| | | | | | | | | | | | | | | | | | | | | 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.
* | | Run cargo update in preparation for next releaseNick Mathewson2022-11-291-147/+157
| | |
* | | Merge branch 'repro-less-shm' into 'main'Nick Mathewson2022-11-291-4/+4
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | reproducible builds without shm Closes #614 See merge request tpo/core/arti!818
| * | | use newer version of zstd and lzmatrinity-1686a2022-11-291-4/+4
| | |/ | |/|
* | | Merge branch 'redacted' into 'main'Ian Jackson2022-11-291-0/+3
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | Define a "redactable" trait, and use it when logging guard info Closes #648 and #627 See merge request tpo/core/arti!882
| * | safelog: Make MaybeRedacted<T> opaque.Nick Mathewson2022-11-281-0/+2
| | |
| * | linkspec: Give a Redacted form for chantarget.Nick Mathewson2022-11-281-0/+1
| |/
* / Draft: Pluggable transport managereta2022-11-281-0/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | This commit implements `PtMgr`, a pluggable transport manager responsible for keeping track of spawned PTs and spawning them to satisfy client requests on demand. It does this in two parts: the `PtMgr` type exported to the rest of the code, and the background `PtReactor` that actually does the spawning; this design ensures that only one attempt to spawn a PT is active at a time, and will prove useful later for implementing e.g. timeouts. A few changes were necessary to the rest of the code in order to make this all work out. Namely: - `TransportRegistry`'s API didn't make any sense for two reasons: - It wasn't feasible for implementors to implement `ChannelFactory`, since that'd require constructing a `ChanBuilder` (which requires a bootstrap reporting event sender). - Treating the PT manager as a registry is over-general; it's only necessary for it to spawn pluggable transports, so saddling it with other concerns didn't make any sense. - (It's possible to get extensibility for arbitrary user customization by just letting the user swap in a new `ChannelFactory`, anyway.) - Therefore, the `PtMgr` implements the new `AbstractPtMgr` trait, which is far more narrowly focused; this only exists to solve a dependency loop, and is documented as such. - This provides a `TransportHelper` instead of a `ChannelFactory`.
* upgrade rustls to 0.20, ignoring all deprecation warningstrinity-1686a2022-11-261-22/+11
|
* tor-linkspec: Provide LoggedChanTarget type alias and utility methodIan Jackson2022-11-231-0/+1
| | | | | This makes it easy to talk about, and construct, a BoxSensitive<OwnedChanTarget>, which is what we'll use in errors.
* tor-basic-utils: Provide helper for serde flexible parsingIan Jackson2022-11-211-0/+1
|
* BridgeConfigBuilder: Introduce build() functionIan Jackson2022-11-211-0/+1
| | | | And test cases for it, and its errors.
* BridgeConfigBuilder: Introduce the struct with the dictionary reprIan Jackson2022-11-211-0/+1
| | | | | | | | | | | 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)
* GuardMgr: Log when a guard status changes (significantly).Nick Mathewson2022-11-171-0/+1
| | | | | | | | | | | | | | | | 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.
* tor-ptmgr: make configuration use builders, plumb into arti-clienteta2022-11-161-0/+2
| | | | | | | 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`.
* Actually, require rsa 0.7.1.Nick Mathewson2022-11-101-2/+2
| | | | rsa 0.7.0 has been yanked.
* Upgrade rsa to 0.7. Closes #613.Nick Mathewson2022-11-101-26/+22
|
* Upgrade to serde_with 2, phf 0.11. Closes #526.Nick Mathewson2022-11-101-50/+135
|
* Upgrade to tinystr 0.7. Closes #591.Nick Mathewson2022-11-101-2/+2
|
* Merge branch 'clap-v3' into 'main'Ian Jackson2022-11-081-40/+35
|\ | | | | | | | | | | | | Upgrade to clap 3 Closes #616 See merge request tpo/core/arti!830
| * Upgrade to clap 3 with minimal changesGabriel de Perthuis2022-11-041-40/+35
| | | | | | | | | | | | | | | | 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>.
* | bridge descs: Apply sensitive() to bridge identity in error log msgIan Jackson2022-11-081-0/+1
| |
* | bridge desc: Implement cache reuse logic and if-modified-sinceIan Jackson2022-11-041-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | bridge desc tests: Apply tracing_test::traced_testIan Jackson2022-11-041-0/+1
|/ | | | This lets us see the log messages. They look fine, as it happens.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 15:41:55 +0000