| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
test-temp-dir: New crate
See merge request tpo/core/arti!1925
|
| | |
| |
| |
| |
| | |
Introduce the crate, move the code motion, and make minimal necessary
changes.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Upgrade to futures-rustls and rustls 0.22.
Closes #1179
See merge request tpo/core/arti!1919
|
| | |
| |
| |
| |
| |
| |
| | |
The futures-rustls crate has supplanted the async-rustls crate,
and it requires/embeds rustls 0.22.
Closes #1179.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
tor-hsservice: replay: Recover from partial writes
Closes #1207
See merge request tpo/core/arti!1920
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Move state_dir to tor_persist and start to implement it
Closes #1205
See merge request tpo/core/arti!1913
|
| | |
| |
| |
| |
| | |
Bring in the fslock-guard crate and replace the Void in the structs.
(Separated out since this contains Cargo.lock churn.)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.)
|
| | |
|
| |
|
|
| |
Closes #1215
|
| |
|
|
|
| |
Provide the last modification time too, since we have it. This allows
handlers to things not contemplated by the convenience API.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
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).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
These crates had no changes previously, but they depend on crates
that had breaking changes themselves.
tor-linkspec
tor-hspow
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |\
| |
| |
| |
| | |
Run cargo-update in preparation for 1.1.12 release
See merge request tpo/core/arti!1854
|
| | | |
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
KeySpecifier improvements
Closes #1126, #1147, and #1151
See merge request tpo/core/arti!1851
|
| | | |
|
| |/
|
|
|
| |
As recommended in the d-a changelog, I'm not calling this a breaking
change to our APIs.
|
| |
|
|
|
|
|
|
| |
```
cargo update -p zerocopy
```
Fixes https://gitlab.torproject.org/tpo/core/arti/-/issues/1174
|
| |
|
|
|
| |
This is to prevent current use of the same directory of replay logs by
different instances.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |\
| |
| |
| |
| |
| |
| | |
Enable use of warn_report etc with anyhow::Error
Closes #1157
See merge request tpo/core/arti!1818
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
Resolve several TODO HSS items in hsrproxy
See merge request tpo/core/arti!1809
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
upgrade to toml 0.8.8
See merge request tpo/core/arti!1794
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
Followups from MSRV 1.70 upgrade
See merge request tpo/core/arti!1785
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|