| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
`tor-dirclient` uses `tor-proto` in its public API, and its `tor-proto`
version was bumped from 0.12.1 -> 0.16.1.
|
| |
|
|
|
|
|
|
|
|
| |
We bumped the minor version of `tor_checkable`, which is used in the
`tor-cell` public APIs (e.g. `Ed25519Cert` implements
`tor_checkable::Timebound`, using `tor_checkable::TimeValidityError`
as its error type).
This bumps the minor version of `tor-cert` (including for its
dependents).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
APIs were broken in these pre-1.0.0 crates:
```
tor-keymgr
tor-config
tor-checkable
tor-circmgr
tor-dirmgr
tor-hsclient
tor-hsservice
tor-hsrproxy
```
Done with:
```
cargo set-version --bump minor -p tor-keymgr
cargo set-version --bump minor -p tor-config
cargo set-version --bump minor -p tor-checkable
cargo set-version --bump minor -p tor-circmgr
cargo set-version --bump minor -p tor-dirmgr
cargo set-version --bump minor -p tor-hsclient
cargo set-version --bump minor -p tor-hsservice
cargo set-version --bump minor -p tor-hsrproxy
```
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
APIs were added:
```
tor-units
tor-cell
tor-proto
tor-netdir
arti-client
```
Done with:
```
cargo set-version --bump patch -p tor-units
cargo set-version --bump patch -p tor-cell
cargo set-version --bump patch -p tor-proto
cargo set-version --bump patch -p tor-netdir
cargo set-version --bump patch -p arti-client
```
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Functional changes were made, but no APIs were added or broken:
```
tor-events (async_broadcast 0.6.0 -> 0.7.0)
tor-netdoc (signature 1 -> 2)
tor-guardmgr
arti-testing (config 0.13.4 -> 0.14.0)
tor-persist (breaking changes gated behind experimental feature)
fslock-guard (fix lockfile_has_path compilation on Windows)
```
Done with:
```
cargo set-version --bump patch -p tor-events
cargo set-version --bump patch -p tor-netdoc
cargo set-version --bump patch -p tor-guardmgr
cargo set-version --bump patch -p arti-testing
cargo set-version --bump patch -p tor-persist
cargo set-version --bump patch -p fslock-guard
```
|
| |
|
|
|
|
| |
This is a temporary workaround for #1307:
In `libc`, struct sigaction doesn't seem to have
the same fields on all the unix platforms.
|
| | |
|
| |\
| |
| |
| |
| | |
Mark code with "TODO 504" and "TODO 789".
See merge request tpo/core/arti!1992
|
| | |
| |
| |
| |
| |
| |
| |
| | |
I've done this by looking for every non-test instance of pick_relays
or pick_n_relays, and for every non-test usage of any non-ID-related
method on Relay or UncheckedRelay.
Part of #504.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Remove a wanted blank line.
|
| | |
| |
| |
| |
| | |
This is not implemented. It is better to have it commented out than
providing a knob that isn't connected to anything.
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This errors such as
```
DEBUG tor_hsservice::svc::publish::backoff: failed to upload a hidden service descriptor: circuit failed attempt=2 can_retry=true
```
into
```
DEBUG tor_hsservice::svc::publish::backoff: failed to upload a hidden service descriptor: could not build circuit to HsDir attempt=2 can_retry=true
```
|
| | |
|
| |
|
|
|
|
|
| |
We should be reporting all IPT errors, not just the ones coming from the
IPTs that are "current".
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1966#note_2996978
|
| | |
|
| |
|
|
|
|
| |
This will enable the `IptManager` to more accurately report its status.
Part of #1083
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
The new `IptError` type represents an IPT error that is definitely
caused by a bad IPT.
`IptError` will be made public and exposed through a variant of the
`Problem` enum used for status reporting.
Part of #1083
|
| |
|
|
|
|
| |
We are about to add a new `IptError` type that is only for errors that
are the IPT's fault (the ones `IptEstablisherError::is_ipt_failure()`
returns `true` for).
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Closes #1083
|
| |
|
|
| |
Part of #1083
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The `IptManager` now reports its status as `Recovering` (with the
`latest_error` set to `IptError::FaultyIpt`) if it doesn't have enough
good IPTs to publish. Its status is `Degraded` if it has published some
IPTs, but needs to establish more.
Note: unconditionally setting `latest_error` to `IptError::FaultyIpt` is
not entirely correct. We will need to get the actual errors, if any,
from the `IptEstablisher`.
Part of #1083
|
| |
|
|
|
|
|
| |
The `OnionServiceStatus` API can now report errors coming from
`IptManager`.
Part of #1083
|
| |
|
|
| |
Part of #1083
|
| |
|
|
|
|
|
| |
`State::Degraded` means we've successfully published a number of
introduction points, but we would like to have more.
Part of #1083
|
| |
|
|
|
| |
Since these are `*StatusSender` APIs, it seems more idiomatic to call
them `send*`.
|
| |
|
|
|
| |
We don't have blank lines between the other variants, so let's remove
this one too for consistency.
|
| | |
|
| |
|
|
| |
Part of #1115
|
| |
|
|
|
|
| |
The offending `ArtiPath` should be included in the error.
Part of #1115
|
| |
|
|
|
|
|
|
|
| |
Originally, these functions converted to and from `ArtiPathComponent`.
In !1931, we replaced `ArtiPathComponent` with `Slug` without renaming
the conversion functions. Since we're converting to and from `Slug` now,
I think it makes sense to rename them too.
Part of #1115
|
| |
|
|
| |
Part of #1271
|
| |
|
|
| |
Part of #1271
|
| |
|
|
|
|
|
| |
NB: `KeyMgr::remove_with_type` will need to be renamed to
`KeyMgr::remove_entry`.
Part of #1271
|
| |
|
|
| |
Part of #1271
|
| |\
| |
| |
| |
| | |
Code cleanup for IPT external state expiry
See merge request tpo/core/arti!1982
|
| | | |
|
| | | |
|
| | | |
|