summaryrefslogtreecommitdiff
path: root/Cargo.lock
Commit message (Collapse)AuthorAgeFilesLines
...
* 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.
* bridge descriptors: TestsIan Jackson2022-11-031-0/+3
|
* bridge descriptors: Provide an implementation of BridgeDescProviderIan Jackson2022-11-031-0/+1
| | | | Tests will come in a moment.
* remove unused dependanciestrinity-1686a2022-10-291-5/+0
|
* Upgrade dependencies in preparation for upcoming release(s)Nick Mathewson2022-10-281-123/+209
|
* BridgeDescProvider: Make BridgeDescEvent repr(u16) and derive traitsIan Jackson2022-10-271-0/+1
| | | | This will enable us to impl FlagEvent for it.
* tor-ptmgr/ipc: First cut of pluggable transport spawningeta2022-10-261-0/+8
| | | | | | | | | | | | | | | | | | | | | | | 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
* FlagEvent trait: Implement using macrosIan Jackson2022-10-251-0/+36
| | | | | | | | | | | 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.
* Merge branch 'guards_as_bridges_part1' into 'main'Nick Mathewson2022-10-241-0/+1
|\ | | | | | | | | Allow GuardMgr to expose bridges as guards (part 1) See merge request tpo/core/arti!785
| * guardmgr: Add bridges sample, encode sample ID in FirstHopId.Nick Mathewson2022-10-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | tor-guardmgr: descs: Make BridgeDescError DynCloneIan Jackson2022-10-211-0/+1
|/
* Merge branch 'pt-serde' into 'main'Nick Mathewson2022-10-201-0/+1
|\ | | | | | | | | serde support for PtTarget See merge request tpo/core/arti!780
| * Implement serde for PtTarget and its members.Nick Mathewson2022-10-201-0/+1
| | | | | | | | This will let us remember bridges that use pluggable transports.
* | chanmgr: Begin a socks-client implementation.Nick Mathewson2022-10-201-0/+1
|/ | | | | | | 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.
* linkspec: Add an "all_overlapping" accessor to ByRelayIds.Nick Mathewson2022-10-181-0/+7
| | | | | | | 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.
* Write tests for RelayIdSet.Nick Mathewson2022-10-151-0/+1
|
* Add builders for OwnedChanTarget/OwnedCircTargetNick Mathewson2022-10-061-0/+2
| | | | | This will become the preferred way to make one of these objects, and insulate us against future API changes.
* Merge branch 'bridge_containers' into 'main'Nick Mathewson2022-10-061-0/+1
|\ | | | | | | | | Start implementing more data structures to hold Bridge descriptors. See merge request tpo/core/arti!755
| * BridgeRelay: Implement more traits.Nick Mathewson2022-10-041-0/+1
| | | | | | | | | | | | 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.
* | remove manual limitation of coredump sizetrinity-1686a2022-10-051-1/+0
|/ | | | it's already disabled by secmem_proc
* tor-linkspec: ByRelayIds<> type to hold a set of HasRelayIdsNick Mathewson2022-10-041-0/+1
| | | | | This is based on the type generated with n_key_set, with a couple of extra methods to take advantage of RelayId and RelayIdRef.
* Merge branch 'hostname-validation' into 'main'Nick Mathewson2022-10-031-0/+7
|\ | | | | | | | | Use hostname-validator crate for hostname validation See merge request tpo/core/arti!739
| * Use hostname-validator crate for hostname validationReylaba2022-10-031-0/+7
| |
* | Merge branch 'multi_keyed_set' into 'main'Nick Mathewson2022-10-031-0/+2
|\ \ | | | | | | | | | | | | Include a HashSet variant that can be keyed on multiple keys. See merge request tpo/core/arti!747
| * | Include a HashSet variant that can be keyed on multiple keys.Nick Mathewson2022-10-031-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | Merge branch 'socks_client' into 'main'Nick Mathewson2022-10-031-0/+22
|\ \ \ | | | | | | | | | | | | | | | | Implement a SOCKS client handshake See merge request tpo/core/arti!746
| * | | Make sure that socks4 auth doesn't have any 0 bytes.Nick Mathewson2022-10-031-0/+1
| | | | | | | | | | | | | | | | | | | | Try to do it in constant time, to avoid even the smell of side-channel attacks.
| * | | Fuzzer code for socks client implementation.Nick Mathewson2022-10-031-0/+21
| |/ /
* | | Oops: propagate bumps to Cargo.lock.Nick Mathewson2022-10-031-3/+3
| | |
* | | Bump patchlevels of binary crates.Nick Mathewson2022-10-031-11/+11
| | | | | | | | | | | | | | | Since these don't expose any Runtime-based APIs, they don't have a breaking change.
* | | Bump minor version of tor-rtcompat and most of its dependentsNick Mathewson2022-10-031-4/+4
| | | | | | | | | | | | | | | | | | | | | (Since the APIs for the `Schedule::sleep*` functions changed, this is a breaking change in tor-rtcompat. Therefore, the Runtime trait in tor-rtcompat is now a different trait. Therefore, anything that uses the Runtime trait in its APIs has also broken.)
* | | Bump crates that have had backward compatible API changes.Nick Mathewson2022-10-031-6/+6
| | |
* | | Run cargo update in preparation for upcoming release.Nick Mathewson2022-09-301-122/+128
| | |
* | | Upgrade dependencies in preparation for upcoming releaseNick Mathewson2022-09-301-13/+56
|/ /
* | Add the skeleton of a tor-ptmgr crateNick Mathewson2022-09-231-0/+12
| | | | | | | | | | When complete, this crate will handle launching and using pluggable transports on demand.
* | Create an API for TransportIdNick Mathewson2022-09-231-0/+2
|/
* enumerate platform with getresuid supporttrinity-1686a2022-09-101-0/+1
|
* Merge branch 'fix-async-std' into 'main'eta2022-09-071-0/+1
|\ | | | | | | | | fix compilation error with async-std See merge request tpo/core/arti!723
| * fix compilation error with async-stdtrinity-1686a2022-09-061-0/+1
| |
* | `TaskSchedule`: give error on `sleep*()` if last handle is droppedNick Mathewson2022-09-071-0/+1
|/ | | | | | | | | | | | | | | | | | 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.
* Merge branch 'update-notify' into 'main'Ian Jackson2022-09-011-193/+68
|\ | | | | | | | | | | | | update to notify v5.0.0 Closes #454 See merge request tpo/core/arti!679
| * update to v5.0.0trinity-1686a2022-08-311-193/+68
| |
* | Bump crate versions in preparation for Arti 1.0.0 release.Nick Mathewson2022-09-011-22/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Because we want to work more on ensuring that our semver stability story is solid, we are _not_ bumping arti-client to 1.0.0 right now. Here are the bumps we _are_ doing. Crates with "minor" bumps have had API breaks; crates with "patch" bumps have had new APIs added. Note that `tor-congestion` is not bumped here: it's a new crate, and hasn't been published before. ``` tor-basic-utils minor fs-mistrust minor tor-config minor tor-rtcompat minor tor-rtmock minor tor-llcrypto patch tor-bytes patch tor-linkspec minor tor-cell minor tor-proto minor tor-netdoc patch tor-netdir minor tor-persist patch tor-chanmgr minor tor-guardmgr minor tor-circmgr minor tor-dirmgr minor arti-client minor arti-hyper minor arti major arti-bench minor arti-testing minor ```
* | Update patch-versions on crates without API changes.Nick Mathewson2022-09-011-13/+13
|/ | | | | | | Since our last round of releases, these crates have had either trivial changes, or changes that did not affect their APIs. Therefore we are bumping their versions, but not changing which versions of them other crates depend on.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 12:00:22 +0000