| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This doesn't yet change the public API, it just begins the work of
plumbing these around throughout `ClientCirc`, `Reactor`, etc.
This can't be broken up into smaller commits without causing build
failures.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
And the same with `single_leg_with_id_mut` and `single_leg_mut`.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
These give more ways of accessing legs.
|
| | | | | | | |
|
| | |/ / / / |
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
maint: Make matrix-check run in parallel in CI.
Closes #1625
See merge request tpo/core/arti!2835
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We should ideally do this for every-crate as well, but since that's
written in bash, it's a little more annoying to do. The options there
are either to rewrite it in python (probably good to do anyways) or to
modify the list_crates script to move the parallelization in there
(useful since it lets us reuse code, but doing that with a generator is
likely not possible). For now I'm just going to file a ticket to do that
and go back to working on stuff i actually should be doing :)
Fixes: #1625
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
cargo_audit: Ignore RUSTSEC-2024-0436 and fix RUSTSEC-2025-0009
See merge request tpo/core/arti!2847
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
`ring` versions < 0.17.12 are affected by [RUSTSEC-2025-0009]
(potential panic when overflow checks are enabled).
I don't believe we are affected, because
* we don't use `ring::aead::quic::HeaderProtectionKey::new_mask`
* operations using `ring::aead::{AES_128_GCM, AES_256_GCM}` can panic
only in very specific circumstances, namely when
encrypting/decrypting 64 gigabytes of data in one go, if overflow
checks are enabled (and Arti never buffers that much data)
[RUSTSEC-2025-0009]: https://rustsec.org/advisories/RUSTSEC-2025-0009
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Remove incorrect deprecation warning in hsc
See merge request tpo/core/arti!2845
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Edit connecting-to-onion.md
See merge request tpo/core/arti!2844
|
| |/ / / / / |
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
tor-rtmock: Actually decorate MockSleepProvider with `#[deprecated]`
See merge request tpo/core/arti!2843
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2843#note_3169975
|
| | | | | |
| | | | |
| | | | |
| | | | | |
For some reason rustfmt wants to mess with this. Forestall it.
|
| | | | | | |
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
MockSleepProvider and MockSleepRuntime have been declared deprecated
by the docs for some time. We're about to mark them `#[deprecated]`.
This commit has been split out for clarity of review.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-proto: Move Circuit to its own module.
See merge request tpo/core/arti!2837
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is mostly code motion + some visibility adjustments.
Moving all of these outside of `reactor` makes it easier to see which
parts are internal vs which are accessed by the reactor. It also helps
us enforce/audit invariants such as 'there should be no contention on
the `CircHop::map` mutex' (the stream map is now private to
`reactor::circuit`, and therefore nothing inside `reactor` will be
directly accessing it).
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This will enable us to move `CircHop` out of `reactor.rs`.
|
| |/ / / /
| | | |
| | | |
| | | | |
This will enable us to factor `Circuit` out of `reactor.rs`.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-dirmgr: Remove `dbg!`
See merge request tpo/core/arti!2838
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
dirmgr: When expiring a consensus, remove its blob from disk.
Closes #1655
See merge request tpo/core/arti!2504
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Here we move the responsibility for removing ExtDoc entries for
vanished blobs into the _caller_ of read_blob(): we want to tidy all
such entries in one go.
Unlike a (reverted) previous approach, this time we don't need a
retry loop.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We'll want to use this information to tell us whether to retry.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
I'm about to add a retry mechanism.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We've already stopped ignoring any DB errors, so we may as well make
sure that any FS errors we encounter are also reported.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will help us keep its members private from the rest
of sqlite.rs, and ensure that things are kept consistent.
(This violates rust formatting for clarity. I'll reindent after.)
|
| | | | | | |
|