| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
The spread should be either `hsdir_spread_store` or
`hsdir_spread_fetch`, depending on whether we're uploading or
downloading descriptors.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The IPT manager is going to want to separate the IptEstablisher
struct (which contains the Drop signal) from the watch receiver.
We could add an accessor to clone the watch, but the copy in the
IptEstablisher would be redundant.
This makes new()'s signature a bit funky but it's an internal method
so I think that's fine.
|
| |/ / / |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
It's simpler to always use a `String` to represent directory request bodies.
We no longer need the `StringBody` trait.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
The hsdir publisher will send the `HsDescUploadRequest`s to the
appropriate directory using `send_request()`.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, the `Requestable` trait assumed the body of the request
would always be empty (`http::Request<()>`). This change replaces the
hardcoded `()` body type with the `Requestable::Body` associated type
(which will allow implementors to create requests with non-empty
bodies). This will enable us to reuse the `Requestable` trait for
building `POST` requests for uploading descriptors.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
`download()` is actually a general-purpose function for sending HTTP
requests on a stream. We will soon repurpose it for `POST`-ing
descriptors, so let's rename it to `send_request`.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-proto: remove unused import
See merge request tpo/core/arti!1493
|
| | |/ /
| | |
| | |
| | |
| | | |
This commit removes an unused import within the test module of the
`tor_proto::circuit` module.
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
arti-client: Make from_directories() derive the keystore_dir from state_dir.
Closes #988
See merge request tpo/core/arti!1498
|
| | | | |
|
| | |/
| |
| |
| | |
Closes #988
|
| |\ \
| | |
| | |
| | |
| | | |
Write more of IptEstablisher.
See merge request tpo/core/arti!1510
|
| | | |
| | |
| | |
| | |
| | | |
It now supports running in a loop, trying to establish an
introduction point, and reporting status.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This will help with making a keep_established method.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Intro points must not send these extensions except in response to a
request that prompts them.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
I had planned to make this code accept extensions of unknown type,
but for now I'm backing out of that plan: the set of extensions we
send influences the set that we're willing to receive.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
doc: fix malformatted comment in SliceWriterError
See merge request tpo/core/arti!1503
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-cert: actually use dangerously_assume_timely
See merge request tpo/core/arti!1497
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
This commit makes a trait function use another currently unused trait
function, thereby increasing the test coverage, as well as being
potentially more correct from a semantic point of view.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
test: provide a test for expired certificates
See merge request tpo/core/arti!1496
|
| | |/ /
| | |
| | |
| | |
| | | |
This commit implements a test for an expired Ed25519 certificate within
the `tor_cert` crate.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
test: encode unrecognized `tor_cert::CertExt`
See merge request tpo/core/arti!1495
|
| | | | | |
|
| | |/ /
| | |
| | |
| | |
| | | |
This commit introduces a test for unrecognized `tor_cert::CertExt`
fields.
|
| | | |
| | |
| | |
| | | |
This comment will form the basis for the protocol name registry.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The `KeypairData` type from [ssh-key] at some point leaked into the
keymgr API (via the `EncodableKey` trait). Instead of re-exporting just
`KeypairData`, let's re-export the entire `ssh_key` crate
(`EncodableKey` implementors would need additional types from `ssh_key`
to construct a `KeypairData` object anyway).
[ssh-key]: https://crates.io/crates/ssh-key
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This helper is no longer needed (the logic from
`parse_ssh_format_erased` changed).
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, the Arti key store would store x25519 secret keys as ed25519
OpenSSH keys, which it would convert to x25519 upon loading (using the
conversion function added in !1297 (merged)). This approach isn't good
enough though: most people will probably want to bring their existing
x25519 keys, and in order to store those in OpenSSH format, we'd need
convert them to ed25519, which is impossible (because the secret part of
an x25519 key contains a SHA512'd secret, whereas the corresponding,
"un-expanded", ed25519 secret key contains the secret itself rather than
the SHA).
Now that `ssh-key` has support for ssh keys with [custom algorithm
names], we can store x25519 in OpenSSH format directly. This commit
changes the storage format used by the keymgr for x25519 client auth
keys (from ed25519-ssh to our own custom key type with an algorithm name
of `"[email protected]"`).
Closes #936
[custom algorithm names]: https://github.com/RustCrypto/SSH/pull/136
|