| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-config: Use a polling watcher on non-windows platforms that don't have inotify.
Closes #1644
See merge request tpo/core/arti!2547
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Part of #1644
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This enables us to make use of the unfortunately-necessary test-specific
code path.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When testing, compare the contents of the files too, not just their
mtime Otherwise, because the polling backend detects changes based on
mtime, if the test creates/writes files too fast, it will fail to notice
changes (this can happen, for example, on a tmpfs).
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The default is 30s, which feels a bit too long.
Also, when testing, we use a much shorter interval.
This is meant to be a temporary solution, so we hard-code the interval
rather than make it configurable.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
inotify.
On windows and platforms that support inotify (i.e. linux and android),
we continue using the recommended watcher. On platforms that use kqueue,
we switch to a polling watcher to work around a [notify bug] that
manifests when using a non-recursive watcher to watch a directory.
This commit is best reviewed with `git diff --ignore-all-space`.
Closes #1644
[notify bug]: https://github.com/notify-rs/notify/issues/644
|
| | | | | | | |
|
| | | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | | |
This type will soon become platform-dependent, so I am preemptively
adding a type alias.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
general::SocketAddr: Specify and implement string representations.
Closes #1681
See merge request tpo/core/arti!2519
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
(This turned up another place where we need documentation.)
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The fuzzer makes sure that whatever we can parse, we can format into
an object that is parsed in the same way.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This matches our parsing, and our general rule that our parser
defers to SocketAddr::from_pathname.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Needed for tests.
|
| | | |_|/ /
| |/| | |
| | | | |
| | | | | |
Closes #1681.
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
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
|