| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Done via:
```
for crate in $(./maint/list-crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.39.0
done
```
|
| |\
| |
| |
| |
| |
| |
| | |
arti: Remove `proxy.socks_port` and `proxy.dns_port`
Closes #2300
See merge request tpo/core/arti!3622
|
| | |
| |
| |
| |
| |
| | |
I'm undecided whether we want to keep `resolve_alternative_specs`
around, but it seems possible/likely that we'll want it in the future,
so I think we can keep it.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This is in preparation for removing the `listen_port` and `dns_port`
config options.
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
fix(minver): Update paste dependency to be minver compatible
See merge request tpo/core/arti!3610
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
For readability.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
The previous name was misleading (the closure asserts the exact
opposite).
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
release: run fixup-features.
See merge request tpo/core/arti!3620
|
| | | | |
|
| |/ /
| |
| |
| | |
Use anyhow::Context to wrap error in useful message.
|
| | |
| |
| |
| | |
This resolves a newly-triggered lint.
|
| | | |
|
| | |
| |
| |
| | |
This adds the lint to all our crates.
|
| | |
| |
| |
| | |
We now need it whether or not http-connect is enabled.
|
| | |
| |
| |
| |
| |
| |
| | |
This isn't the long-term solution to error reporting and proxies,
but it is a start that we can work from.
Closes #2304.
|
| |/ |
|
| | |
|
| |
|
|
|
| |
This commit adds more documentation/examples for the prop330 syntax for
specifying directory authorities.
|
| |\
| |
| |
| |
| |
| |
| | |
Make all non-main APIs in arti experimental.
Closes #2284, #2299, and #419
See merge request tpo/core/arti!3586
|
| | | |
|
| | |
| |
| |
| | |
Closes #2299.
|
| | |
| |
| |
| | |
No semantic changes.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Or rather, un-rename it. It's no longer a stable thing, so it
doesn't need to have this particular name.
|
| | |
| |
| |
| |
| |
| | |
Only fn main() is now pub when experimental-api is disabled.
Closes #2284.
|
| |/ |
|
| |
|
|
|
| |
The dependencies of futures-copy got bumped in arti!3570, leading to a
change in futures-copy, hence why we bump the patch version.
|
| |\
| |
| |
| |
| | |
Bump dependencies for 1.9.0
See merge request tpo/core/arti!3570
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Done using the following:
```bash
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.38.0
done
```
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Fixes bug introduced in 0cc367b9fef37c0f7d7f04d54c4687b27ef251d0.
Without this fix, RPC's get_proxy_info command wouldn't work.
|
| |/
|
|
|
|
|
| |
Executed command:
```
cargo run -p fixup-features -- --exclude examples/ --exclude maint/ Cargo.toml
```
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This will make it easier to see the correspondence between CTorPaths
and the HS client/service key specifiers.
Initially, I was hoping this would make it easier to write a d-d macro
that automatically derives a `CTorPath` variant (e.g.
`HsClientDescEncKeypair`) from the KeySpecifier type name
(`HsClientDescEncKeypairSpecifier`), but alas, I don't think d-d can
"chop off" name suffixes ("Specifier", in this case).
`from_ctor_path()`/`ctor_path()` implementations for converting
`CTorPath`s to and from key specifiers.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Out of all the variants in `KeyPathError`, `Unrecognized` is the odd one
out, because unlike the others, which are mainly just lower level
parsing errors, `Unrecognized` is a higher level error constructed in
`KeyMgr::describe()`.
`KeyMgr::describe()` now returns an `Option`, because
* the failure to describe a user provided `KeyPath` may or may not be
an error
* previously, `describe()` would only ever return `Ok` or
`Err(KeyPathError::Unrecognized)`, which essentially a binary
result. Also, `describe()` would never return any of the other
`KeyPathError` kinds, which further suggests `Unrecognized`
doesn't belong there
The `Unrecognized` variant still exists, but is now part of
`KeystoreCorruptionError`, (returned from
`KeyMgr::validate_entry_integrity()`).
|
| |
|
|
|
| |
C Tor keystore entries now use the same output format as the non-C Tor
entries.
|
| |
|
|
| |
This folds `display_arti_entry()` into `display_entry()`.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This is no longer needed now that `KeyMgr::describe()` works on
`CTorPath`s.
Removing this special handling has the added bonus that the keymgr CLI
output is now uniform for all keystores (before this change, `keys list`
used a slightly different output format for displaying C Tor entries).
The corresponding tests will be updated in a future commit.
|
