| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | | |
| | | | |
| | | | |
| | | | | |
torspec!499 is merged.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
With facility to test roundtrip of whole consensus.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I have confimed the consent of the operators of the relays listed in
the script.
The rationale for using .entire.FOO filenames for the curl outputs
will become clear shortly.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Nothing in CI tests incomplete without retain-unknown, apparently.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It doesn't make sense to say that a plain consensus is an "ns"
consensus, because "ns" stands for "network status" and all consensus
flavours, and indeed votes, are network statusus.
That's why tor-netdoc now uses "plain". Use that here too.
|
| | | | | | |
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Update spin to 0.9.8
See merge request tpo/core/arti!4208
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes cargo-audit failure, due to spin 0.9.8 being yanked:
The changelog entry for 0.9.9 says:
> ### Fixed
>
> - Unsoundness in `Once::force_into_inner`, `Once::try_into_inner`, and
> `Once::into_inner_unchecked`. \[...]
In our stack, spin <- lazy_static 1.5.0 (only). lazy_static
1.5.0 (git tag) has no hits for `into_inner`. So I think we don't
have any calls to the previously-unsound methods.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
maint/cargo-audit: Bump crossbeam-epoch to address RUSTSEC-2026-0204
See merge request tpo/core/arti!4207
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
RUSTSEC-2026-0204 doesn't affect Arti, so this won't need a TROVE.
I checked using the procedure documented under "Checking whether we are
affected by a RUSTSEC" in `doc/dev/SecurityResponse.md`. I applied the
following patch to my local `crossbeam-epoch` to remove the affected
impls, and confirmed that Arti still builds successfully with it:
```diff
diff --git a/crossbeam-epoch/src/atomic.rs b/crossbeam-epoch/src/atomic.rs
index 41b4cd91..8b9b3a01 100644
--- a/crossbeam-epoch/src/atomic.rs
+++ b/crossbeam-epoch/src/atomic.rs
@@ -939,14 +939,6 @@ impl<T: ?Sized + Pointable> fmt::Debug for Atomic<T> {
}
}
-impl<T: ?Sized + Pointable> fmt::Pointer for Atomic<T> {
- fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
- let data = self.data.load(Ordering::SeqCst);
- let (raw, _) = decompose_tag::<T>(data);
- fmt::Pointer::fmt(&(unsafe { T::deref(raw) as *const _ }), f)
- }
-}
-
impl<T: ?Sized + Pointable> Clone for Atomic<T> {
/// Returns a copy of the atomic value.
///
@@ -1660,12 +1652,6 @@ impl<T: ?Sized + Pointable> fmt::Debug for Shared<'_, T> {
}
}
-impl<T: ?Sized + Pointable> fmt::Pointer for Shared<'_, T> {
- fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
- fmt::Pointer::fmt(&(unsafe { self.deref() as *const _ }), f)
- }
-}
-
impl<T: ?Sized + Pointable> Default for Shared<'_, T> {
fn default() -> Self {
Shared::null()
```
Note: the reason the `fmt::Pointer` impls I removed above look slightly
different from the ones in the [crossbeam-rs MR] from the RUSTSEC page
is because my patched `crossbeam-epoch` is based on the
`crossbeam-epoch-0.9.18` tag rather than `main`.
[crossbeam-rs MR]: https://github.com/crossbeam-rs/crossbeam/pull/1273/files
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
multiple crates: Fix clippy warnings
See merge request tpo/core/arti!4203
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | |/ /
| |/| | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Upgrade cipher, aes, and ctr.
See merge request tpo/core/arti!4195
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Negotiate flowcontrol-cc and CGO on onion services
Closes #2473 and #1948
See merge request tpo/core/arti!4135
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This saves us from having to check whether it is 0, and better
represents what the type is allowed to be.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I had incorrectly thought that this was necessary.
Fortunately, @opara looked at the spec. :)
We do, however, still need to _advertise_ negotiate_subproto.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We put this behind a feature because we probably want to test this
out before we enable it.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The "flow-control" item is documented in proposal 324 section 9.1;
there's a ticket (torspec#418) to document it.
The "proto" item is documented at
https://spec.torproject.org/rend-spec/hsdesc-encrypt.html#item:proto
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will simplify the case where we need to look up
a particular extension in an ExtList.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We _already_ do not include FLOWCTRL_CC as a listed protocol among
the capabilities we provide, when we make a virtual hop. This
branch will make that behavior even more certain, by not looking at
required-client-protocols any longer.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We do something similar with non-virtual hops at !4076.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We'll want this for the flow-control line in hsdescs.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
The patch looks complicated, but this is just code movement.
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
tor-netdoc: rangemap_mutate_range: New function
See merge request tpo/core/arti!4190
|
