| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It's error-prone to have to remember e.g. that "Desc=5"
means "family ID support", so in torspec!251 we added mnemonic names
like DESC_FAMILY_IDS.
Here we use those names in tor-protover.
|
| | | | | |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
replace state_dir and storage_mistrust with tor_persist::state_dir::StateDirectory
See merge request tpo/core/arti!2863
|
| | | | |
| | | |
| | | |
| | | | |
tor_persist::state_dir::StateDirectory
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Impose a maximum on our fallback estimated timeout
Closes #1693
See merge request tpo/core/arti!2842
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The fallback timeout is the one that we use when we have
insufficient data. We reset our observations, and maybe rebuild
our circuits, when we find that too many circuits have failed
recently. When we do so, we double our fallback timeout.
Previously we had no limit, which could lead to overflow (#1693).
In this commit we impose a maximum of 2 hours,
which is ridiculously high.
(C tor uses a maximum of INT32_MAX seconds, which is even more
ridiculously high.)
Closes #1693.
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
Port to rand 0.9
See merge request tpo/core/arti!2869
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The constructor for rand::distr::Uniform is now fallible,
so it makes sense to bubble up its restrictions.
This is a breaking change.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
(This applies to every crate that has an API that takes a
`rand::Rng` or any related trait.)
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
- The Rng::gen() functions have been renamed to Rng::random().
|
| | | | | |
| | | | |
| | | | |
| | | | | |
- Several methods have been moved out of SliceRandom.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- `rand::thread_rng()` has been deprecated and renamed to `rand::rng()`
(I missed these cases because they were from prelude::*)
|
| | | | | |
| | | | |
| | | | |
| | | | | |
- `Uniform::new_inclusive` is now fallible.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
- The Standard distribution has been renamed to StandardUniform.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
- `try_fill_bytes()` is no longer a member of RngCore.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
dalek-cryptography is still on rand 0.8, so we need a compatibility
shim for the Rng.
Fortunately, since we merged interface-abstraction-of-the-daleks
(!2868), we no longer need to propagate this compatibility layer
throughout our codebase.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
- `Rng::gen_range()` has been renamed to `Rng::random_range()`
|
| | | | | |
| | | | |
| | | | |
| | | | | |
- The rand::distributions module has been renamed to rand::distr
|
| | | | | |
| | | | |
| | | | |
| | | | | |
- `rand::thread_rng()` has been deprecated and renamed to `rand::rng()`
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
(Per discussion at #1774, we think the changes are acceptable.)
This commit won't compile on its own; subsequent commits will fix it.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously we used the version signature::rand_core for some reason,
but that's now incompatible.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is partly for consistency, and partly to facilitate
a global search-and-replace.
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
hsc: remove onion-address flag in favour of stdin
Closes #1630
See merge request tpo/core/arti!2861
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Add `quite` to the common arguments
* Substitute dialoguer in favor of `read_line` in `get_onion_address`
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* The user will be prompted interactively for the onion-address
to prevent onion-address leaking in shell history
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Wrap x25519-dalek and ed25519-dalek types.
See merge request tpo/core/arti!2868
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
With this change, we'll no longer need to expose the types from
dalek-cryptography as part of our API, and we'll have more freedom
to switch ed25519 implementations, or to upgrade to a newer
`rand` ahead of their schedule.
Unlike with x25519-dalek, I had to tweak the API a bit: There's no
way to get a &PublicKey out of a Keypair now, and implementing the
old ed25519-dalek traits seemed unnecessary.
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
With this change, we'll no longer need to expose the types from
dalek-cryptography as part of our API, and we'll have more freedom
to switch curve25519 implementations, or to upgrade to a newer
`rand` ahead of their schedule.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
rpc-client: Increase test coverage for the msgs module
See merge request tpo/core/arti!2865
|
| | |/ / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
arti: hsc-key-get: Print LF after discovery key
See merge request tpo/core/arti!2856
|
| | | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | | |
Did not print a newline after service discovery key. Looked bad.
Prints newline now. Looks better.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-cell: Add constructors for the conflux cell types.
See merge request tpo/core/arti!2858
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
We will soon need these in the circuit reactor.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Per <https://spec.torproject.org/dir-spec/netdoc.html>,
our netdocs never have a BOM, and never have internal NULs.
This makes Arti reject such documents.
For arguments on why it's okay to increase parser strictness,
see the (forthcoming) proposal 356 at torspec!342,
and see older discussion at torspec#296.
Closes #1739.
|
| | |_|/ / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I'm about to make our parsers reject some strings at construction
time, so it makes sense to have these functions become fallible.
This is a breaking change.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-keymgr: Resolve TODOs from key_specifier::tests
Closes #1889
See merge request tpo/core/arti!2849
|