| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | |
| | | | | |
Added ConfigBuildError::MissingOneOf and did TODO
See merge request tpo/core/arti!4131
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
Upgrade rdrand dependency to 0.9
See merge request tpo/core/arti!4194
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Starting with rdrand 0.9, the crate supports aarch64.
|
| | | | | | |
|
| |/ / / / |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
added Unix Socket support
See merge request tpo/core/arti!4129
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4141#note_3430551
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
"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.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | | | |
|
| | |/ / /
|/| | | |
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Suggested by opara in
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4145#note_3430815
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now that relays no longer use `CtrlCmd::AwaitStreamRequests`, some of
these fields are unused. I'm leaving them in for now, but we should
remove them if they're still unused after we finish the circ reactor
impl.
I'm not removing `AwaitStreamRequests`, because it will be needed by
onion services, when we replace the old client circuit reactor with the
new one.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We don't need it anymore now that `RelayCirc`s always allow incoming
stream requests.
The previous design, where you could build a `RelayCirc` that didn't
allow stream requests, was a leftover from the onion service
`ClientCirc` implementation that this was inspired from (onion services
*do* need the two to be decoupled, because incoming stream requests are
only allowed on the virtual hop, after it's established).
Closes #2582
|