| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
|
| | | |
| | |
| | |
| | | |
Closes #1455 [PATCH 4(v2)/4]
|
| | | |
| | |
| | |
| | | |
Part of #1455 [PATCH 3(v2)/4]
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Part of #1455 [PATCH 2(v2)/4]
- Rework sshkeygen::ed25519_encoded to also work as replacement for
sshkeygen::exists
- Drop sshkeygen::exists
- Rename sshkeygen::{ed25519_encoded -> sshkeygen_ed25519_strings}
- Pull out sshkeygen_ed25519_strings from mod sshkeygen
- Drop mod sshkeygen
|
| | | |
| | |
| | |
| | | |
_sigh_
|
| | | |
| | |
| | |
| | | |
Closes #1455 [PATCH 4/4]
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Part of #1455 [PATCH 3/4]
Abstract of the test(s):
Encoded (key) A -> Decoded (key) A
Decoded A -> Encoded B
Encoded B -> Decoded B
Assert that Decoded A == Decoded B
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Part of #1455 [PATCH 2/4]
Utils include:
- mod sshkeygen
- sshkeygen::exists - check if ssh-keygen is available
- sshkeygen::ed25519_encoded - generate encoded Ed25519 keys
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Part of #1455 [PATCH 1/4]
ssh_key::{PrivateKey, PublicKey}::to_openssh requires feature alloc
|
| |/ /
| |
| |
| |
| |
| |
| | |
TestSpecifier::new(prefix: ...) -> new(suffix: ...)
Prefix is given by TestSpecifier::path_prefix() which returns
const TEST_SPECIFIER_PATH = "..."
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
fix compiling fs-misstrust on tvOS
See merge request tpo/core/arti!2890
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-circmgr: Explicit type annotation
See merge request tpo/core/arti!2886
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit adds an explicit type annotation to the learning_timeouts()
function, as leaving it out yielded an error while trying to compile
tor-circmgr in a project that had this crate deep down in its supply
chain.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
tor-keymgr: Implemented test improvements
Closes #1888
See merge request tpo/core/arti!2848
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Cleanups related to rpc configuration
Closes #1309 and #1830
See merge request tpo/core/arti!2887
|
| | | | |
| | | |
| | | |
| | | | |
Closes #1830.
|
| | | | |
| | | |
| | | |
| | | | |
Closes #1309.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
tor-proto: simplify `ConfluxSet::circuit_action`
See merge request tpo/core/arti!2884
|
| | | | |
| | | |
| | | |
| | | | |
I also added an additional non-doc TODO comment.
|
| | | | |
| | | |
| | | |
| | | | |
As far as I can tell, the extra drop handling code isn't needed anymore.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
I think the return type is simplified enough now that we don't need
this.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now returns only the first item of the stream rather than the stream
itself. We use this in `Reactor::run_once`, which means we only ever use
the first item anyways.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We'll want to add more text here, but that should probably wait
until we have a permanent home for the rendered RPC documentation.
(see #1829)
|
| | |/ /
|/| | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Cleanups and followups for rand 0.9 choose_multiple_weighted and friends.
Closes #1903
See merge request tpo/core/arti!2880
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Instead of doing the more sensible thing when every relay has weight
0, give a warning message.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Here we test the (arguably inconsistent behavior) where can we
return fewer items than requested if no item had zero weight.
(If this ever becomes an error, we need to modify the calling code.)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
WeightedError::InsufficientNonzero is expected under some
circumstances, but the other instances would mean that we have a
bug.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
We want to make sure that behavior for 0-weighted elements is
consistent for choose_multiple_weighted and choose_weighted.
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-proto: Replace RunOnceCmdInner with CircuitCmd in Circuit impl
See merge request tpo/core/arti!2881
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2881#note_3178624
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There is no `Multiple` counterpart in `CircuitAction`, so the `Single`
variant name doesn't make much sense.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The `LegId` is now added by the caller, when converting the resulting
`CircuitCmd`s to `RunOnceCmdInner`.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
`CircuitCmd`s are a subset of `RunOnceCmdInner`, and don't have a
`LegId`.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
A `CircuitCmd`, unlike `RunOnceCmdInner`, doesn't know anything about
`LegId`s. The user of the `CircuitCmd`s is supposed to know the `LegId`
of the circuit the `CircuitCmd` came from. This is necessary because
circuits don't know (and can't know) their own `LegId`.
The various `Circuit` operations (e.g. `handle_cell`) will soon be
updated to return `CircuitCmd` instead of `RunOnceCmdInner` (because the
`RunOnceCmdInner` variants will soon be updated to also have an
associated `LegId`, and `Circuit`s don't have access to their `LegId`s).
The calling code, which *does* know the `LegId`, will then map
`CircuitCmd`s to `RunOnceCmdInner`.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This tells the reactor which circuit leg the input message originated
from.
Addresses a TODO.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We want to require that whenever we generate a key that's persistent
(stored in KeyMgr), it's going to be made from a stronger-than-usual
Rng. This trait helps us enforce that.
We also add a FakeEntropicRng struct to use for testing.
Note that this turned up a case that we'd missed, which required
an internal change in tor-hsservice.
|
| | | | | | |
|