summaryrefslogtreecommitdiff
path: root/Cargo.lock
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Run cargo update again, in preparation for releaseNick Mathewson2022-08-311-15/+16
|
* Merge branch 'compact_home_2' into 'main'Nick Mathewson2022-08-311-0/+1
|\ | | | | | | | | | | | | Represent the home directory as ${HOME} or %UserProfile% Closes #555 See merge request tpo/core/arti!700
| * fs-mistrust: Add a `anonymize_home` extension fn for Path.Nick Mathewson2022-08-311-0/+1
| | | | | | | | | | | | This function transforms `/home/nickm/.config` to `${HOME}/.config/`, so that we can expose the username less in our logs.
* | Merge branch 'refactor-anyhow-arti-crate' into 'main'Nick Mathewson2022-08-311-1/+0
|\ \ | | | | | | | | | | | | Remove `anyhow` from `tor-config` crate See merge request tpo/core/arti!707
| * | Remove `anyhow` from `tor-config` crateArturo Marquez2022-08-281-1/+0
| | |
* | | Run cargo update in preparation for release.Nick Mathewson2022-08-301-119/+122
| | |
* | | Upgrade serial_test in preparation for release.Nick Mathewson2022-08-301-5/+17
| | |
* | | Upgrade statrs in preparation for release.Nick Mathewson2022-08-301-6/+32
| | |
* | | Add functionality to listen for SIGHUPs.Nick Mathewson2022-08-261-0/+13
|/ /
* | Merge branch 'safelog_more' into 'main'Ian Jackson2022-08-261-0/+1
|\ \ | |/ |/| | | | | Apply safelog to more of the things that we log See merge request tpo/core/arti!693
| * tor-chanmgr: don't log addresses so much.Nick Mathewson2022-08-251-0/+1
| | | | | | | | | | We now log connection attempts at debug!, and mark relay target addresses as sensitive.
* | arti: cfg: Rename `*_port` to `*_listen` and change the typeIan Jackson2022-08-251-0/+1
| | | | | | | | | | | | | | 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.
* | tor-config: Provide misc::ListenIan Jackson2022-08-251-0/+1
| |
* | tor-basic-utils: Provide IoErrorExt is_not_a_directory()Ian Jackson2022-08-251-0/+1
|/ | | | | We're going to want this functionality, which isn't in the stable stdlib.
* arti_client: Refuse to build a client if we are setuid.Nick Mathewson2022-08-241-0/+1
| | | | | | Arti is not designed to be a setuid-safe program. Part of #523.
* tor-cell: PaddingNegotiate::start: take IntegerMillisecondsIan Jackson2022-08-171-0/+1
|
* channel padding: Test through most of the layersIan Jackson2022-08-171-0/+1
|
* channel padding: Send negotiation cellsIan Jackson2022-08-161-0/+1
|
* Introduce ChannelConfigIan Jackson2022-08-161-0/+3
| | | | | This commit is just the necessary plumbing. The config is currently empty. We'll add something to it, for padding control, later.
* tor-config: Introduce PaddingLevelIan Jackson2022-08-161-0/+1
| | | | This will be used for controlling channel padding, for now.
* tor-proto: padding::Parameters: use impl_standard_builderIan Jackson2022-08-161-0/+1
| | | | | | | 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.
* arti: Add support for process hardeningNick Mathewson2022-08-151-0/+13
| | | | | | | | | | | | | 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.
* Merge branch 'less_arti_surface' into 'main'Nick Mathewson2022-08-111-0/+1
|\ | | | | | | | | | | | | Reduce the arti crate's API surface; improve semver documentation. Closes #522, #530, and #532 See merge request tpo/core/arti!664
| * arti: Move most public APIs behind `experimental-api`.Nick Mathewson2022-08-111-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | tor-congestion: implement the RTT estimation algorithm from prop#324eta2022-08-111-0/+10
| | | | | | | | | | | | | | | | | | | | | | 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.
* | Merge branch 'main' into 'linkspec_refactor_v3'Nick Mathewson2022-08-101-26/+7
|\ \ | | | | | | | | | # Conflicts: # crates/tor-netdir/semver.md
| * | Update shellexpand, and switch to non-forkIan Jackson2022-08-051-26/+5
| |/ | | | | | | | | | | | | | | 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`.
| * New SecretBuf type in tor-bytesNick Mathewson2022-08-011-0/+1
| | | | | | | | | | | | | | | | | | 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.
| * Use the `zeroize` feature in several cratesNick Mathewson2022-08-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | tor-proto: Unify the check_match code in channel and handshakeNick Mathewson2022-08-101-0/+1
| | | | | | | | | | | | | | | | | | | | 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.
* | tor-netdir: Add a static assertion about RelayIdType::COUNTNick Mathewson2022-08-101-0/+1
| | | | | | | | | | | | | | 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.)
* | Parsing, encoding, and serde for RelayId.Nick Mathewson2022-08-101-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | Add a set of Identity-related types and accessors.Nick Mathewson2022-08-101-0/+2
| | | | | | | | | | | | | | 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.
* | Implement serde traits on RelayIds.Nick Mathewson2022-08-021-0/+1
|/ | | | | This will allow RelayIds to replace IdPair in tor-guardmgr. (The fields are named accordingly with `serde(rename)`.)
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 19:17:20 +0000