| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
|
|
|
| |
Done with:
```
cargo set-version --bump minor -p tor-hsclient
cargo set-version --bump minor -p arti-rpcserver
cargo set-version --bump minor -p tor-hscrypto
cargo set-version --bump minor -p tor-cell
```
|
| | |
|
| |\
| |
| |
| |
| | |
arti-client: Rename KeyStore to Keystore.
See merge request tpo/core/arti!1359
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`KeyStore` was renamed to `Keystore` globally in !1355. This fixes a
compile error caused an unfortunate series of non-conflicting (from
git's POV) but incompatible merges:
* !1356 added a line threferencing an error variant that capitalizes the
"s" in "KeyStore" (`ErrorDetail::KeyStore`)
* !1356 landed just before !1355 (the global renaming). Since there was
no conflict between the 2, we're now in a state where the code added
in !1356 is referencing an `ErrorDetail` variant that no longer
exists.
|
| |\ \
| | |
| | |
| | |
| | | |
Add a missing "experimental-api" rustdoc notation
See merge request tpo/core/arti!1353
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
Run fixup-features on current `main`
See merge request tpo/core/arti!1352
|
| | | |
| | |
| | |
| | |
| | | |
Some of these seem spurious: it looks like fixup-features resolved
an issue and then complained about it too. I'll investigate further.
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | | |
keymgr: Rename KeyStore to Keystore globally.
See merge request tpo/core/arti!1355
|
| | |/
| |
| |
| |
| | |
We've been capitalizing the "s" in "KeyStore" inconsistently. This
`s/KeyStore/Keystore/g` across the codebase.
|
| |/
|
|
| |
This `From` impl was just calling itself recursively...
|
| |\
| |
| |
| |
| | |
keymgr: Validate ArtiPaths, replace HsClientSpecifier with generic ArtiPathComponent
See merge request tpo/core/arti!1262
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
`ArtiPathComponent` is a more generic version of `HsClientSpecifier`.
|
| |\ \
| | |
| | |
| | |
| | | |
arti-client: Add keystore_dir to StorageConfig.
See merge request tpo/core/arti!1312
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Part of #891
|
| | | |
| | |
| | |
| | | |
Part of #891
|
| | | |
| | |
| | |
| | | |
Part of #891
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Mark all {hs,onion-serivce}-client features as non-experimental.
Closes #896
See merge request tpo/core/arti!1347
|
| | |/ |
|
| | | |
|
| | |
| |
| |
| | |
As per IRC discussion, re lack of Vanguards.
|
| |/
|
|
|
| |
These tests include tests of .onion, which we are disabling by
default. So we must make some prefs that enable them.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This variant can never be constructed when parsing a TorAddr, so it
doesn't make sense to have it in TorAddrError: the use can never see
it unless they enable `error_detail`.
Not a semver break because the client feature is not yet stable.
Closes #932.
|
| |
|
|
| |
Apply deferred rustfmt churn.
|
| |
|
|
| |
Apply deferred clippy churn.
|
| |
|
|
|
| |
Invent a trait a la circmgr config for the hs client connector config.
Plumb a suitable value all the way through to the code that will use it.
|
| |
|
|
|
|
|
| |
We put this in `[address_filter]`.
The interaction with the corresponding stream preference is a bit
complicated. We must turn the stream pref into a `BoolOrAuto`.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Doing this causes TorClientBuilder to become Send. I also add a
test to ensure that TorClientBuilder remains Send in the future.
This isn't a semver break, but only because DirProviderBuilder is
marked with `experimental-api`.
Closes #924
|
| |
|
|
| |
Otherwise we'll fill up our RAM with junk.
|
| | |
|
| |
|
|
|
| |
`dummy.rs` will be moved to `tor-keymgr`, which will export everything
from the module.
|
| | |
|
| |\
| |
| |
| |
| | |
lints: Promote clippy::print_stderr and clippy::print_stdout
See merge request tpo/core/arti!1271
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
keymgr: Remove Error::NotFound, update KeyMgr, KeyStore APIs.
See merge request tpo/core/arti!1280
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes the `NotFound` `tor_keymgr::Error` variant. Since `KeyMgr`
and `KeyStore` users will need to be able to distinguish between "not
found" errors and other I/O errors, this also changes the return types
of the `get()` and `remove()` functions of `KeyStore` and `KeyMgr`,
which now return `Ok(None)` instead of `Error::NotFound`.
This makes the `KeyStore` API consistent with `KeyMgr::get`, which
already has a return type of `Result<Option<K>>` (rather than
`Result<K>`).
This also prepares us for #901, which will make key store errors
opaque. Without this change:
* we'd have to create a `struct NotFoundError;` error type. Its
`HasKind` impl would need to return a new
`ErrorKind::KeyStoreErrorNotFound` `ErrorKind` variant
* callers would have to match the `error_kind()` of the error to
figure out whether the key simply can't be found
(`ErrorKind::KeyStoreErrorNotFound`), or if something went wrong
(any other `ErrorKind`).
Given the above, I think `Result<Option<()>>` makes for a more ergonomic
API.
Part of #901
|
| |\ \
| | |
| | |
| | |
| | | |
Fix a rustdoc link.
See merge request tpo/core/arti!1274
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | | |
Upgrade a couple of dependencies
See merge request tpo/core/arti!1276
|
| | |/ |
|