| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
| |
This was a little funny, since the other storage elements are
declared in tor-client. Fortunately, our stacked configuration
logic handles this fine.
|
| | |
|
| |
|
|
|
| |
This allows applications to find out where arti is listening when
arti has been configured to listen with the port "auto".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the proxy and dns modules only had "be a proxy"
functions that ran forever. Now they have functions that bind to
listeners and return a separate "be a proxy" future that runs
forever.
This lets us simplify some kludges in subcommands::proxy. More
importantly, it will let us return the bound-to ports so that
subcommands::proxy can write them to disk.
This is a break in experimental-apis, which does not require a
semver change.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
We don't rely on this within the arti crate, and tor-rtcompat already
sets this. It's confusing to have it here as well. If the arti ecosystem
requires this, it should be enabled on the lower level crates (like it
already is in tor-rtcompat) so that arti-client users get it too.
|
| |
|
|
|
|
|
|
|
| |
Fixes part of #2193.
(Edits from nickm: I selected the cases here that I could verify
were correct from immediate context.)
Edited-by: Nick Mathewson <[email protected]>
|
| |\
| |
| |
| |
| | |
Update to derive-deftly 1.6.0
See merge request tpo/core/arti!3525
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This has:
* Fixes to hygiene spans from the new modules feature, needed for
my WIP netdoc encoder derive.
* A substantially richer `${error }` construct.
|
| |\ \
| |/
|/|
| |
| | |
Add `KeyMgr` accessor to `TorClient`
See merge request tpo/core/arti!3442
|
| | |
| |
| |
| |
| |
| | |
`run_check_integrity`
This change simplifies the signature of `run_check_integrity`.
|
| |\ \
| | |
| | |
| | |
| | | |
release: Bump metrics-exporter-prometheus
See merge request tpo/core/arti!3521
|
| | | |
| | |
| | |
| | | |
Part of #2278
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
tor-config: Refactor `Listen` to make usable for arti-relay
See merge request tpo/core/arti!3469
|
| | | |
| | |
| | |
| | | |
Assumes that 0.37.0 will be the next version number.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Done using:
```
cargo set-version --bump minor -p arti
```
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.37.0
done
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The non-{arti-,tor-} crates are:
```
./maint/list_crates | rg -v '^(tor|arti)'
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
retry-error
futures-copy
```
We split them in the following categories:
* crates with no changes (no version bumps): None
```
maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-'
```
* crates that only have non-functional changes (bump the patch version,
but not the dependend-on version):
- oneshot-fused-workaround
- slotmap-careful
- test-temp-dir
- fslock-guard
- equix
- caret
- safelog
- retry-error
* crates where functional changes were made, but no APIs were added or broken:
- hashx
- fs-mistrust
- futures-copy
* crates where APIs were broken (bump minor): None
The bumps from this commit were created using this script:
```
PATCH_NF=(
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
equix
caret
safelog
retry-error
)
PATCH="
hashx
fs-mistrust
futures-copy
"
./maint/bump_nodep "${PATCH_NF[@]}"
for crate in $PATCH; do
cargo set-version --bump patch -p $crate;
done
```
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Run fixup-features in preparation for release
See merge request tpo/core/arti!3510
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
arti: Put supported request headers in Tor-Capabilties
Closes #2259
See merge request tpo/core/arti!3473
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
This is for spec conformance; it is a missing piece of prop365.
Closes #2259.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix some errors in and around making directories for logfiles.
Closes #2240, #2265, and #2266
See merge request tpo/core/arti!3491
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This will improve the error message for problems similar to
arti#2240, if they recur.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This should fix the main part of arti#2240.
This is an instance of arti#2267 ("Path::parent has funny behavior")
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
arti: Add rate_limit_at_intro to the example config
See merge request tpo/core/arti!3493
|
| | | | | | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
This is mostly c&p from the `rate_limit_at_intro` docs, I just added an
extra paragraph to clarify the meaning of the tuple elements (i.e.
`(rate, burst)`).
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
hsservice: Clarify what max_concurrent_streams_per_circuit does
See merge request tpo/core/arti!3492
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
At first glance, this might seem equivalent to C Tor's
`HiddenServiceMaxStreams` option, but it's actually
`HiddenServiceMaxStreamsCloseCircuit` (Arti doesn't implement the
former).
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
http-connect: use end reason for http status if possible
See merge request tpo/core/arti!3481
|