| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
1. Move `impl From<SpecificKeypair> for curve25519::StaticKeypair`
(which was just a bespoke impl for HsClientDescEncKeypair)
into the define_pk_keypair macro, so everything has it.
Currently the only other user of the curve25519_pair feature is HsSvcNtorKey.
2. Provide the reverse conversion too.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
use ipv6 runner instead of tpa for coverage
See merge request tpo/core/arti!1754
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
tor-persist: Make LockStatus #[must_use]
See merge request tpo/core/arti!1753
|
| | | |
| | |
| | |
| | |
| | | |
I see other problems with this API, see #1136. but we can at least
easily do this.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Deps and lockfile: Don't use tor-error and retry-error from crates.io
See merge request tpo/core/arti!1752
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
tor-log-ratelim mistakenly had a non-path dependency.
Changing this, and running `cargo fetch --offline` to update the
lockfile, causes the build to prefer in-tree for many entries in the
lockfile.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
tor-rtmock: introduce spawn_join() for MockRuntime & MockExecutor
See merge request tpo/core/arti!1746
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This makes it synchronous. The trait bounds on the return type
have also been relaxed to not require Clone
|
| |/ /
| |
| |
| |
| |
| |
| | |
This helps abstract away the need to create a oneshot channel in order
to get the return value out of an async function when using MockRuntime.
ref: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1727#note_2965352
|
| |\ \
| | |
| | |
| | |
| | | |
tor-hsservice: Clarify a message
See merge request tpo/core/arti!1750
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Tbis will result in "some message ...: the error" which I think is OK.
We don't use a Unicode single-character ellipsis because that
character can be hard to read at font sizes which are otherwise OK for
text, and because use of non-ascii in logfiles and error messages is
unecessary and might cause unnecessary trouble (for example, if the
log messages end up going somewhere which isn't 100% valid UTF-8).
|
| |/ /
| |
| |
| |
| | |
Possibly at some point in the past, matching a slice directly wasn't
possible. But it is now.
|
| |\ \
| |/
|/|
| |
| | |
HSS publisher, do some work on ReactorErrors
See merge request tpo/core/arti!1724
|
| | |
| |
| |
| |
| |
| |
| | |
It might come back.
This introduces a new bug relating to logging, but it does abolish one
of the variants of ReactorError.
|
| | |
| |
| |
| | |
IHNI why rustfmt wants to do this *now*
|
| | |
| |
| |
| |
| |
| | |
We're going have it in an variant in FatalError.
Also make it impl HasKind and have IptError delegate to that.
|
| | |
| |
| |
| | |
And explain why this isn't just a question of merging it with FatalError.
|
| | |
| |
| |
| | |
The call to reactor.run() in publish.rs, launch(), calls warn_report.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
tor-keymgr: Support encoding more than one denotator in an ArtiPath.
Closes #1093 and #1112
See merge request tpo/core/arti!1747
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Closes arti#1112
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
tor-hscrypto: Deprecate HsClientIntroAuth{Key, Keypair}.
Closes #1037
See merge request tpo/core/arti!1749
|
| | |
| |
| |
| |
| | |
`HsClientIntroAuthKeypair` is deprecated and no longer used as an
"encodable key".
|
| | |
| |
| |
| | |
Closes #1037
|
| | | |
|
| | |
| |
| |
| | |
(fmt).
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
We need to add a module-global `#[allow(deprecated)]` to silence the
deprecation warnings coming from the derived `derive_more` impls of the
2 newly deprecated structs. Since we don't want the `allow` to apply to
the entire `pk` module, let's put `HsClientIntroAuthKey` and
`HsClientIntroAuthKeypair` in a separate module and apply the
`#[allow(deprecated)]` there.
|
| | |
| |
| |
| | |
Part of #1037
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
HSS: Send DosParams extension to introduction points.
Closes #723
See merge request tpo/core/arti!1740
|
| | | | |
|
| | | |
| | |
| | |
| | | |
It's available when the HsIntro=5 subprotocol version is present.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
It does not help that C tor has a set of parameters and a set of
configuration options with exactly the same names which configure
the same thing in two slightly different ways.
|
| | | |
| | |
| | |
| | | |
Closes #723.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
We want the configuration, at least, so that we can see our DoS
settings. I expect we'll also want the watcher so that we can
see _changes_ in the DoS settings.
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
tor-keymgr: Rewrite define_key_specifier using derive-adhoc.
Closes #1093
See merge request tpo/core/arti!1733
|
| | | | |
|