| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
arti: remove 'relay' subcommand and 'arti-relay' dependency
See merge request tpo/core/arti!2542
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
memquota features, preparation
See merge request tpo/core/arti!2545
|
| | | | | |
| | | | |
| | | | |
| | | | | |
(fmt)
|
| | | | | |
| | | | |
| | | | |
| | | | | |
It's not documented anywhere ATM. I will do that in a followup MR.
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
This will allow us to make `tor-memquota/memquota` enabled by default,
without forcing it to be compiled in everywhere.
I don't change that in this MR, though.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
rpc spec: Start to document method naming convention
Closes #1678
See merge request tpo/core/arti!2539
|
| | | | |
| | | |
| | | |
| | | | |
Closes #1678.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
All but one of our current methods follows this convention,
and we're about to rename it.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Update to pwd-grp 1.x to fix NetBSD build
See merge request tpo/core/arti!2540
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Should fix the build on NetBSD, see rust-pwd-grp#4.
Also, eliminates the last use of derive-adhoc, the old name for
derive-deftly.
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
Use clippy to prevent non-mq use of mpsc::channel
Closes #1659
See merge request tpo/core/arti!2536
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
We have a ticket for this. But the ticket number was wrong, so fix that.
|
| | | |
| | |
| | |
| | |
| | | |
We need to decide whether RPC will participate in memquota.
Perhaps it should. But that's for the future.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
These are the call sites where using this fucntion is correct.
(Outside tor-rtmock, which we'll do separately.)
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Abolish `_ => panic!()`
See merge request tpo/core/arti!2534
|
| | | | | |
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Abolish use of python-is-python3
See merge request tpo/core/arti!2535
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
"python" meaning "python3" was a wrongheaded decision by Python
upstream. Our python scripts should start (roughly) `#! env python3`.
And, this is already the case - we don't actually use python-is-python3!
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Abolish the toplevel Account
See merge request tpo/core/arti!2537
|
| | | | |
| | | |
| | | |
| | | | |
Fixes a TODO.
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
We'll need this to allow `ToplevelAccount::new_noop` (eg, in tests)
when the type of ToplevelAccount changes.
We have to do this via an extension trait.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-relay-crypto: Temporarily comment out RelaySigningKeySpecifier.
See merge request tpo/core/arti!2527
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The `RelaySigningKeySpecifier` is currently defined as:
```rust
#[non_exhaustive]
#[derive(Deftly, PartialEq, Debug, Constructor)]
#[derive_deftly(KeySpecifier)]
#[deftly(prefix = "relay")]
#[deftly(role = "KP_relaysign_ed")]
#[deftly(summary = "Relay medium-term signing keypair")]
/// The key sepcifier of the relay medium-term signing key (RelaySigningKeypair)
pub struct RelaySigningKeySpecifier;
```
This means there can only be a single `relaysign_ed` key with an
`ArtiPath` of the form `relay/KP_relaysign_ed`. This is a problem,
because relays storing their identity key offline will want to generate
a number of `relaysign_ed` keys ahead of time, so we need the keystores
to be able to contain multiple such keys. We will need their `ArtiPath`
to encode a variable component (for example, a timestamp).
We also need to teach `KeyMgr` to retrieve such keys (`KeyMgr::get`
should return the first key that has a valid and timely certificate).
This will involve extending the `KeySpecifier` trait with a function for
obtaining the `KeySpecifier` of the certificate of the key, if there is
one.
For now, let's comment it out and rethink its `ArtiPath` as part of
#1692.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
memquota: Document the actual behaviour re streams/circuits
See merge request tpo/core/arti!2531
|
| | | |/ /
| |/| |
| | | |
| | | | |
As per decision in #1661.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
arti: Bump secmem-proc to fix the build errors on FreeBSD.
Closes #1686
See merge request tpo/core/arti!2533
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The FreeBSD fixes were released in [`secmem-proc 0.3.4`].
Closes #1686
[`secmem-proc 0.3.4`]: https://github.com/niluxv/secmem-proc/pull/11
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
tor-keymgr: Add missing docs for keypair_specifier.
See merge request tpo/core/arti!2532
|
| | | | |
| | | |
| | | |
| | | | |
This breaks up a long statement to improve readability.
|
| |/ / /
| | |
| | |
| | |
| | | |
This is a follow-up to !2393, which added support for the
`key_specifier` top-level attribute.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Proof-of-work client
See merge request tpo/core/arti!2486
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Cover some of the novel edge cases we're introducing around object
parameters and repetition. This still feels awfully ad-hoc, but it's
better than nothing.
Co-authored-by: Micah Elizabeth Scott <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We should not be restricting pow-params to occur only once at the rule
level, and we shouldn't be disallowing object parameters at that level
either. Instead, the v1 scheme itself needs to check for and disallow
objects. Future schemes may allow object parameters.
Test cases for this will be added in a subsequent commit.
Co-authored-by: Micah Elizabeth Scott <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Looks like a copy/paste error.
Co-authored-by: Micah Elizabeth Scott <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This proliferates the canned hsdesc inner doc testing strategy, adding
another file with data encoded with onion-pow-example running on C
tor. Tests that it parses successfully, and asserts that the pow params
line contents are correct. This is a positive test only.
This strategy seems problematic, but it's better than nothing.
Co-authored-by: Micah Elizabeth Scott <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Adds another breadcrumb as requested so new folks happening upon this in
the docs can get oriented.
Co-authored-by: Micah Elizabeth Scott <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This can now notice pow_params lines which are invalid because they have
no parameters.
Co-authored-by: Micah Elizabeth Scott <[email protected]>
|
| | | |
| | |
| | |
| | | |
Co-authored-by: Micah Elizabeth Scott <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of min/max pairs, we can use clamp. And since it's a little
clearer, let's go a bit further and use the same clamp construct with a
lower bound of zero in the other spot we had a min().
Co-authored-by: Micah Elizabeth Scott <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Feedback from the hs-pow code review, the internal seed heading member
should be seed_head instead of seed, for consistency. Very low impact
change since the field name is not public.
|
| | | |
| | |
| | |
| | | |
Co-authored-by: Micah Elizabeth Scott <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Effort type didn't have any const constructor and we had to
disassemble it to do any arithmetic. This adds a const constructor and
int/float saturating arithmetic methods.
Co-authored-by: Micah Elizabeth Scott <[email protected]>
|