summaryrefslogtreecommitdiff
path: root/Cargo.lock
Commit message (Collapse)AuthorAgeFilesLines
...
| * | tor-hsservice: replay: partial write test, skeletonIan Jackson2024-01-251-0/+1
| | |
* | | Introduce tor_persist::slug moduleIan Jackson2024-01-251-0/+1
|/ / | | | | | | | | | | | | | | | | I need this for state_dir (#1163, !1853). I intend that this should be used for arti paths (#1092, #1193). See also #1195. Implements the spec in #1192 but doesn't connect it to anything yet.
* | Merge branch 'state' into 'main'Ian Jackson2024-01-241-0/+4
|\ \ | |/ |/| | | | | | | | | Move state_dir to tor_persist and start to implement it Closes #1205 See merge request tpo/core/arti!1913
| * state-dir: Use a real lock guardIan Jackson2024-01-241-0/+1
| | | | | | | | | | Bring in the fslock-guard crate and replace the Void in the structs. (Separated out since this contains Cargo.lock churn.)
| * state-dir: Move from tor-hsservice to tor-persistIan Jackson2024-01-241-0/+3
| | | | | | | | | | | | | | | | | | | | And, instead of being a hidden module, it's a public experimental one. I have feature-gated all the new dependencies since we probably want to feature-gate this module in perpetuity, since some builds of Arti won't need it. Closes #1205
* | fslock-guard: use winapi to test file-equivalency on windowsNick Mathewson2024-01-231-0/+1
|/
* fslockguard: implement a delete_lock_file function.Nick Mathewson2024-01-231-0/+1
|
* Use fslock-arti-forkNick Mathewson2024-01-231-1/+11
|
* fslock-guard: sketch implementationNick Mathewson2024-01-211-0/+7
| | | | | | | This is not yet "correct", since it will rely on https://github.com/brunoczim/fslock/pull/15 (Conceivably, it might be better to make the `fslock` crate rm-safe.)
* proto: Use log_ratelim to report problems delivering BEGIN messges.Nick Mathewson2024-01-171-0/+1
|
* tor-keymgr: Use keystore_error_kind() to get the error kind.Gabriela Moldovan2024-01-151-0/+1
| | | | Closes #1215
* state_dir sketch: Pass more information to disposeIan Jackson2024-01-121-0/+1
| | | | | Provide the last modification time too, since we have it. This allows handlers to things not contemplated by the convenience API.
* tor-hsservice: todos: Use log_ratelim at one call siteIan Jackson2024-01-111-0/+1
|
* Examples using hyper v1ramidzkh2024-01-111-6/+109
|
* tor-hsclient: Derive the KeySpecifier implementation.Gabriela Moldovan2024-01-101-0/+1
| | | | | | | | This addresses a `TODO HSS` about deriving the `KeySpecifier` implementation for client key specifiers. Note that we no longer have a key specifier type for intro auth keys (which are not supported anyway, see #1037).
* Upgrade to latest serial_testNick Mathewson2024-01-091-4/+4
|
* Bump to latest erased-serde.Nick Mathewson2024-01-091-12/+3
|
* Followup patchlevel bumpsNick Mathewson2024-01-091-2/+2
|
* Followup minor version bumps.Nick Mathewson2024-01-091-2/+2
| | | | | | | | These crates had no changes previously, but they depend on crates that had breaking changes themselves. tor-linkspec tor-hspow
* Patchlevel version bumps in preparation for 1.1.12.Nick Mathewson2024-01-091-5/+5
| | | | | | | | | | | | | This crate doesn't have a meaningful public API, so it just gets a patchlevel bump: arti These crates had nonbreaking changes, and get a patchlevel bump: tor-rtcompat fs-mistrust tor-llcrypto tor-cert
* Breaking version bumps in preparation for 1.1.12.Nick Mathewson2024-01-091-29/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These crates have breaking changes on their own: tor-error tor-netdoc tor-dirmgr tor-keymgr Because of the breaking change in tor-error, and the fact that basically every crate publicly depends on tor-error (by implementing ErrorKind), we need to call this a breaking change on all of the following: tor-config tor-geoip tor-rtmock tor-log-ratelim tor-rpcbase tor-bytes tor-hscrypto tor-socksproto tor-cell tor-proto tor-netdoc tor-netdir tor-persist tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr tor-keymgr tor-hsclient tor-hsservice tor-hsrproxy arti-client arti-rpcserver arti-config arti-hyper arti-testing
* Merge branch 'update-20240108' into 'main'Nick Mathewson2024-01-091-266/+273
|\ | | | | | | | | Run cargo-update in preparation for 1.1.12 release See merge request tpo/core/arti!1854
| * Run cargo-update in preparation for 1.1.12 releaseNick Mathewson2024-01-081-266/+273
| |
* | Merge branch 'keyspec' into 'main'Ian Jackson2024-01-081-0/+1
|\ \ | |/ |/| | | | | | | | | KeySpecifier improvements Closes #1126, #1147, and #1151 See merge request tpo/core/arti!1851
| * KeySpecifier tests: add a TimePeriod testIan Jackson2024-01-041-0/+1
| |
* | Update to derive-adhoc 0.8Ian Jackson2024-01-021-7/+34
|/ | | | | As recommended in the d-a changelog, I'm not calling this a breaking change to our APIs.
* Bump zerocopy 0.7.29 -> 0.7.31Jim Newsome2023-12-181-4/+4
| | | | | | | | ``` cargo update -p zerocopy ``` Fixes https://gitlab.torproject.org/tpo/core/arti/-/issues/1174
* tor-hsservice tests: replay: Provide for a filesystem lockfileIan Jackson2023-12-131-0/+1
| | | | | This is to prevent current use of the same directory of replay logs by different instances.
* tor-persist: Provide FsMistrustErrorExt, and use itIan Jackson2023-12-131-0/+2
| | | | | | | | | | | | | This code needs fs_mistrust::Error and tor_error::ErrorKind. I think we probably don't want fs_mistrust to depend on tor_error or vice versa. tor_persist is approximately the place where these two threads of thought come together, and it's currently the lowest place where this is needed. Use it in tor-dirmgr too, which is currently the other place that embodies this knowledge about fs_mistrust::Error.
* Merge branch 'report-anyhow' into 'main'Nick Mathewson2023-12-121-0/+2
|\ | | | | | | | | | | | | Enable use of warn_report etc with anyhow::Error Closes #1157 See merge request tpo/core/arti!1818
| * tor-error: tests: Demonstrate warn_report on bare error and anyhowIan Jackson2023-12-121-0/+2
| |
* | Merge branch 'todo_hsrproxy' into 'main'Nick Mathewson2023-12-111-0/+1
|\ \ | |/ |/| | | | | Resolve several TODO HSS items in hsrproxy See merge request tpo/core/arti!1809
| * hsproxy: Add a rate-limited log for forwarding errors.Nick Mathewson2023-12-071-0/+1
| |
* | ClientCir: use ntor_v3 handshake when target supports itJim Newsome2023-12-071-0/+1
|/
* Merge branch 'new-toml' into 'main'Nick Mathewson2023-12-071-12/+22
|\ | | | | | | | | upgrade to toml 0.8.8 See merge request tpo/core/arti!1794
| * upgrade to toml 0.8.8Nick Mathewson2023-12-051-12/+22
| |
* | Update zerocopyIan Jackson2023-12-061-4/+4
| | | | | | | | | | | | | | | | | | | | | | The version in our lockfile was yanked because of this bug https://github.com/google/zerocopy/pull/672 Our use of zerocopy is only via ahash and AFAICT it doesn't provide it with any affected types. It's not clear to me if the bug is an unsoundness bug. There isn't a RustSec advisory atm.
* | tor-keymgr: Make DefaultKeySpecifier generate a key info extractor as well.Gabriela Moldovan2023-12-051-0/+1
| |
* | tor-keymgr: Add a way of registering key info extractors using inventory.Gabriela Moldovan2023-12-051-0/+1
|/
* Merge branch 'msrv-followup' into 'main'Nick Mathewson2023-12-041-7/+0
|\ | | | | | | | | Followups from MSRV 1.70 upgrade See merge request tpo/core/arti!1785
| * guardmgr: Stop using now-needless retain_mut crate.Nick Mathewson2023-11-301-7/+0
| |
* | tor-hsservice: Define key specifiers for IPT keysIan Jackson2023-12-041-0/+1
| |
* | Two more patchlevel bumpsNick Mathewson2023-12-041-2/+2
| | | | | | | | | | | | | | | | | | These crates both depend on tor-error. Since tor-error got a patchlevel bump, they now depend on the new version, which means by our rules that _they_ get a patchlevel bump themselves. tor-geoip tor-rpcbase
* | Bump minor versions in preparation for releaseNick Mathewson2023-12-041-27/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This crate is new, and gets a bump to 0.1.0. tor-log-ratelim This crate had a breaking change: tor-persist tor-llcrypto had a breaking change. These crates _are_ tor-llcrypto, or (transitively) depend on it. I am assuming that they all re-expose something from it in a way that matters: tor-llcrypto tor-bytes tor-hscrypto tor-socksproto tor-checkable tor-cert tor-linkspec tor-cell tor-proto tor-netdoc tor-consdiff tor-netdir tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr tor-keymgr tor-hsclient tor-hsservice tor-hsrproxy arti-client arti-rpcserver arti-hyper
* | Bump patchlevel versions in preparation for releaseNick Mathewson2023-12-041-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These crates had backward-compatible changes, and get a patchlevel bump only: fs-mistrust tor-error tor-config tor-rtcompat tor-rtmock This crate exposes no non-CLI APIs, and gets a patchlevel bump only: arti
* | Run cargo-update in preparation for release.Nick Mathewson2023-12-041-231/+275
| |
* | Move from `trust-dns` to `hickory`Andrew2023-11-301-26/+25
|/ | | | | | This is not a change of ownership but just rebranding. Signed-off-by: Andrew <[email protected]>
* Require config ≥ 0.13.4Nick Mathewson2023-11-291-2/+2
| | | | | | | This version of the config crate includes a fix for the issue (https://github.com/mehcode/config-rs/issues/464) that had prevented us from using the format we had wanted for our rproxy configuration.
* Merge branch 'semver-breaking-upgrade-of-the-daleks' into 'main'Nick Mathewson2023-11-291-197/+131
|\ | | | | | | | | | | | | Convert to the latest versions of dalek-cryptography Closes #808 See merge request tpo/core/arti!1767
| * Remove RngCompatExt.Nick Mathewson2023-11-291-25/+18
| | | | | | | | | | | | | | | | | | | | This code was needed with the old version of dalek-cryptography, which wasn't compatible with up-to-date versions of the `rand` crate(s). But now that we've upgraded, we can drop this. (We could have left it around and deprecated it, but we are already making a breaking change to tor-llcrypto by upgrading dalek-cryptography.)