| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
| | |
| | |
| | |
| | |
| | | |
We don't need to be logging the entire descriptor for each upload
attempt (logging descriptors immediately after they are generated should
be sufficient).
|
| | | |
| | |
| | |
| | |
| | |
| | | |
The message is supposed to print how many HSDirs the descriptor was
uploaded to (previously it was showing the
`<success_count>/<failure_count>` which is pretty unintuitive).
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This is what the C Tor HsDirs want.
|
| | | | |
|
| |/ / |
|
| |\ \
| |/
|/|
| |
| | |
Bump ahash to 0.8.5.
See merge request tpo/core/arti!1699
|
| |/
|
|
|
|
|
| |
`ahash 0.8.3` has been [yanked], which is causing the cargo audit
job to fail.
[yanked]: https://github.com/tkaitchuck/aHash/wiki/Yanked-versions
|
| |\
| |
| |
| |
| | |
Netdoc time formats (Arti:751)
See merge request tpo/core/arti!1693
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Update download-manager example to match download location
See merge request tpo/core/arti!1691
|
| | | |
| | |
| | |
| | |
| | |
| | | |
It seems download-manager example has fallen out of sinc with files
under https://dist.torproject.org/torbrowser/. This updates the
example to match online files so download can succeed.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Fix rustdoc link warnings/errors.
See merge request tpo/core/arti!1690
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Remove an "HSS" from a "TODO HSS" comment in ptmgr
See merge request tpo/core/arti!1676
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This isn't actually onion service related, AFAICT.
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | | |
tor-keymgr: Auto-generate missing keys in descriptor publisher
See merge request tpo/core/arti!1688
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is not an error, it just means we need to wait until some IPTs are
established.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We don't need this helper anymore (we no longer map `None` to
`Err(MissingKey)`, because the new get-or-create functions don't return
an `Option`).
Also, the key lookups are going to look less uniform from now on
(because some will be auto-generated with `get_or_generate`, and others
with `get_or_generate_with_derived`).
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
necessary.
This auto-generates the blinded identity key and the descriptor signing
key (if they are missing).
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We're already fetching the descriptor signing key from the keystore.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Sometimes it's useful to have the ability to derive the `HsIdKey` from
the keypair (for example, if we've just read the `HsIdKeypair` from the
keystore and also need the `HsIdKey`, this `From` impl enables us to
derive the public part of the key, instead of having to read it from the
keystore).
|
| | | | | | |
|
| | | |_|/
| |/| | |
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
tor-hsservice: Log newly generated HsIds.
See merge request tpo/core/arti!1689
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The condition for logging the "generated a new identity.." message was
wrong (`generate_with_derive()` returns `Some(())` if it generated a new
key, and `None` if the key was already present).
|
| | | | | |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Sometimes it's useful to have the ability to derive the `HsIdKey` from
the keypair (for example, if we've just read the `HsIdKeypair` from the
keystore and also need the `HsIdKey`, this `From` impl enables us to
derive the public part of the key, instead of having to read it from the
keystore).
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Refactor the stream-closing logic in tor-proto
Closes #1065
See merge request tpo/core/arti!1681
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Because dropping a `StreamTarget` causes the circuit reactor to send
an End, the previous do-nothing implementation of `discard()` wasn't
sufficient to cause the request to be ignored without sending an
End.
This commit modifies our "close pending stream" behavior to only
optionally send an End message. To avoid confusion, I'm using a new
`CloseStreamBehavior` enum rather than an `Option<End>`, since we
had previously used `None` in some cases to indicate a default
(misc) end message.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Now that every state-change function consumes the IncomingStream,
there is no longer any reason to keep track of an internal state
enum.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Now that IncomingStream doesn't implement Drop, we can just
destructure it.
|
| | | |
| | |
| | |
| | |
| | | |
Since dropping a StreamTarget will send an End, we don't need
to call reject_internal in this case.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now that `StreamMap::terminate` no longer panics, and now that it
permits the kind of double-call that we allow, we can close #1065.
Closes #1065.
|
| | | |
| | |
| | |
| | |
| | | |
The rule is that we allow up to one explicit `close_pending`,
followed by exactly one final `mpsc::Sender` drop.
|