| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
| | | |
| | | |
| | | |
| | | | |
"Pattern" is wrong. Everything here is a pattern. This field is
the *address* pattern as opposed to the *ports* pattern.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
impl From<IpNet>, Copy, Hash
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Run cargo-update and fix deprecation warnings
See merge request tpo/core/arti!4187
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
time::format_description::parse is now deprecated;
the replacement we want to use is first available in time 0.3.49.
|
| | | | | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
proto: Pass the allowed incoming commands to CreateRequestHandler
Closes #2606
See merge request tpo/core/arti!4177
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Tests that the customizable `IncomingCmdChecker` added for #2606 is
doing its job, by ensuring that the circuit reactor doesn't emit
`IncomingStream`s for incoming streams created with commands that are
not in the reactor's allow list.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The `CreateRequestHandler` now passes the list of allowed "incoming
stream request" commands (i.e. BEGIN, BEGIN_DIR, or RESOLVE) to the
reactor, replacing the hard-coded command list.
Closes #2606
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This enables us to make these configurable: any relays that are not
configured to be an exit will exclude BEGIN and RESOLVE from their list
of allowed commands, causing exit and DNS streams to be rejected as soon
as the BEGIN/RESOLVE cell is received in the circuit reactor.
Context: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4145#note_3430345
Part of #2606
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Remove semver.md files
See merge request tpo/core/arti!4186
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
CI; Mark check-api-surface as may-fail
See merge request tpo/core/arti!4185
|
| | | | |
| | | |
| | | |
| | | | |
See #2616.
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| |_|/ / /
|/| | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Closes #2617.
We've lucked out this time, and it turns out that every one of our
published crates gets a minor bump. So this was generated with:
```
for cr in $(./maint/list-crates); do
cargo set-version -p $cr --bump minor
done
```
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
Run "fixup-features" and clean up the result.
See merge request tpo/core/arti!4180
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It was both in "metrics" and in "experimental"; I think the latter
was intended.
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Update changelog for Arti 2.5.0
See merge request tpo/core/arti!4179
|
| | | |/ / /
| |/| | | |
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Update release date for 2.5.0
See merge request tpo/core/arti!4183
|
| |/ / / / |
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of doing an O(n) check every time we add an unrecognized
protocol, we just scan the list of unrecognized protocols
after we sort them.
Closes #2601.
Resolves TROVE-2026-027.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Add Windows compatibility for maint/add_warning
See merge request tpo/core/arti!4084
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-basic-utils: Don't include '-' in random hostnames
See merge request tpo/core/arti!4178
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
deps: Upgrade anyhow in 'Cargo.lock' (RUSTSEC-2026-0190)
See merge request tpo/core/arti!4174
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This resolves unsoundness in anyhow (RUSTSEC-2026-0190).
https://rustsec.org/advisories/RUSTSEC-2026-0190.html
> Affected versions of this crate violate borrow rules, resulting in
> undefined behavior, when the user adds context to an error via
> `Error::context` and then later calls `Error::downcast_mut` on the
> returned `Error`.
I don't see us calling `downcast_mut()` on any errors. It's possible
something outside of the arti code base is calling it, but I think it's
unlikely.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Derive more Eq in tor-cert and tor-netdoc
See merge request tpo/core/arti!4150
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This commit derives PartialEq and Eq on the "core" certificate types in
lib.rs, i.e. the Ed25519 certificates and its adjacent data types.
We will need this for proper PartialEq and Eq handling in tor-netdoc at
one point.
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
arti-relay: Set incoming stream filters via the CREATE handler
Closes #2582 and #2577
See merge request tpo/core/arti!4145
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Suggested by opara in
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4145#note_3430815
|
| | | | | | |
|