| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We don't support this yet, see #727.
|
| |/ / / / / /
| | | | | |
| | | | | |
| | | | | | |
As mentioned in #727, this is not supported yet.
|
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug 1613: Add support for inserting externally generated and removing arbitrary service discovery keys
Closes #1613
See merge request tpo/core/arti!2396
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
remove_service_discovery_key methods
|
| | | |_|_|/
| |/| | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-guardmgr: Convert a TODO into a NOTE.
Closes #1352
See merge request tpo/core/arti!2405
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This behavior is OK, so this doesn't need to be a TODO.
See the discussion at
https://gitlab.torproject.org/tpo/core/arti/-/issues/1352#note_3015217
Closes #1352
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Revisions to rpc-meta-draft
See merge request tpo/core/arti!2386
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Diziet prefers this terminology; we'll defer a reckoning here
till #849 is resolved.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Instead of saying "no errors before authentication",
we now say "no syntax errors ever."
This should be easier to implement.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
(This is obsoleted by arti-rpc-client-core.)
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Notably, identifiers SHOULD be C identifiers,
and everything has a namespace.
Reserve "rpc" as a namespace for things that were previously
unnamespaced.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is probably still far too informal, but it is better than our
previous documentation.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
(Note what isn't implemented,
and one more kind of authentication we'll likely build someday.)
|
| | | | | | |
|
| |/ / / /
| | | |
| | | |
| | | | |
(Markdown convention deprecates having more than one top-level heading.)
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
tor-hsservice: Improve descriptor publisher status reporting
Closes #1216 and #1572
See merge request tpo/core/arti!2397
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
netdirs (fmt).
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This allows us to set SRVs for example (needed because by default, the
test `NetDir` is built from a consensus that doesn't contain any SRVs).
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We will need to return a list of descriptor upload errors.
We can't return a `Vec<RetryError<DescUploadError>>` here because
`DescUploadError` is a lower-level error type that can't express that
e.g. the upload timed out.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We never return `UploadError::Timeout` (timeouts are represented as
`BackoffError::Timeout`).
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This type is a `Result`, renaming for clarity.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
The descriptor publisher docs live in the `publisher` module.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Closes #1216
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This makes it clearer that some of these functions are essentially
infallible.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This enables us to report a "broken" service status if restricted
discovery is enabled but the authorized_clients list is empty.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Closes #1572
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Currently, the `DegradedReachable` status is only reported by the the IPT
manager and `DegradedUnreachable` is unused.
Soon we'll the publisher reporting `DegradedReachable` or
`DegradedUnreachable` or `Running`, depending on how the descriptor
uploads went.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will allows us determine the ComponentStatus of the publisher
(it'll be either `Running` or `Degraded`, depending on whether the
upload failed).
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
After uploading the descriptor, the publisher transitions into the
`Idle` state. This transition happens even if the upload was
unsuccessful, so it shouldn't cause the onion service status to become
`Running` (because `Running` implies the service is fully reachable, and
if the publisher failed to upload the descriptor to some or all HsDirs,
that won't necessarily be the case).
A future commit will set the publisher's onion svc `State` to
`Running`/`Recovering`/`Broken` according to the upload status.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This resolves a TODO.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously, these were stored in the immutable state behind a mutex, but
since they're not really immutable (we update them if the config
changes), it makes more sense to put them in `State`.
|