| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This variant can never be constructed when parsing a TorAddr, so it
doesn't make sense to have it in TorAddrError: the use can never see
it unless they enable `error_detail`.
Not a semver break because the client feature is not yet stable.
Closes #932.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
keymgr: Add support for x25519 keys.
Closes #900
See merge request tpo/core/arti!1321
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The `Unsupported` variant is no longer needed now that we support
`KeyType::X25519StaticSecret`s.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This also fixes a bug which caused the function to always return a
type-erased `()` instead of the actual key!
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This previously just re-exported `ssh_key::Algorithm`.
However, we will need to support x25519 keys (which aren't supported by
the `ssh_key` crate), so we define our own enum for the key algorithm.
In addition to the `Algorithm` variants from `ssh_key`, our enum also
has an `X25519` variant.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
arti cfg tests: exception declaration improvements
See merge request tpo/core/arti!1330
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
It's used for declarations only, and they should all be here.
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
As per discussion in
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1320#note_2916689
and IRC followup.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Resolve a few "TODO HS" items in circmgr.
See merge request tpo/core/arti!1322
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These two functions are only slightly different, and benefit from
taking a Fn.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I looked through the C tor source code and couldn't find any
additional path restrictions.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
One of these is test-related; one is vanguards-related.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Documentation, mostly on channel and circuit lifecycles
See merge request tpo/core/arti!1318
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Adjust formatting, add more references to lower-level APIs, and
clarify lifetimes a little more.
|
| | | | | | | |
|
| | | | | | | |
|
| | |/ / / / |
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Remove spurious todo-hs items in tor-cert.
See merge request tpo/core/arti!1311
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I am not sure why we wrote these comments, but they are incorrect:
I've investigated the C code and found only 3 key types. The
"unimplemented" types that the TODO comment here complains about are
in fact certificate types.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
keymgr: Downgrade "TODO hs" to "TODO HSS".
See merge request tpo/core/arti!1334
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | | |
These TODOs can be deferred for now: we're not declaring the keymgr APIs
stable until we add support for hidden services.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
tor-hsclient: Make RendPtIdentityForError use RelayIds
See merge request tpo/core/arti!1335
|
| | | | |
| | | |
| | | |
| | | | |
Since arti!1233 this is trivial.
|
| |/ / /
| | |
| | |
| | |
| | | |
For some reason this wasn't used in the actual errors,
although it *was* used in the types of the functions etc.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-hsclient: Discuss intro circuit extend-and-reuse
See merge request tpo/core/arti!1298
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This is a summary of a discussion I had on IRC.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
keymgr: Remove/downgrade a few "TODO hs"
See merge request tpo/core/arti!1328
|
| | | | |
| | | |
| | | |
| | | | |
These don't need to be blockers for the next release.
|
| | | | |
| | | |
| | | |
| | | | |
These were tackled in #901.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-hsclient: Add configuration settings
See merge request tpo/core/arti!1305
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conceptually this is a fixup to
HS configuration: Add retry parameters to configuration
which erroneously removed these comments - they were intended to apply
to *all* these parameters, not just the max attempts.
Not marking it as fixup! because that would involve merge conflicts.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Explain why this fallback to MAX is good.
Discussion
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1305#note_2915927
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Apply deferred rustfmt churn.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Apply deferred clippy churn.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Invent a trait a la circmgr config for the hs client connector config.
Plumb a suitable value all the way through to the code that will use it.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I think these should go in `[circuit_timing]`. That section already
has some retry parameters, so is not strictly *timing*.
This is not honoured yet.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We put this in `[address_filter]`.
The interaction with the corresponding stream preference is a bit
complicated. We must turn the stream pref into a `BoolOrAuto`.
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Missing semver entry for new dirclient API from !1323
See merge request tpo/core/arti!1327
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-hsclient: Completely hide hsdir identities in errors
See merge request tpo/core/arti!1326
|