| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| |
| | |
Version bumps for arti 1.5.0
See merge request tpo/core/arti!3206
|
| | | |
|
| | |
| |
| |
| |
| | |
We've promised in our README not to bump MSRV in patchlevel
releases. So now this is 1.5.0.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Per policy, we bump the minor version of every tor-*, arti-* crate
on each release.
We have updated our MSRV, so we're treating this as a breaking
change for our non-(arti/tor)-prefixed crates too.
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Upgrade to criterion 0.7
Closes #2026
See merge request tpo/core/arti!3199
|
| | |
| |
| |
| |
| |
| | |
Closes #2026.
We can do this now that criterion-cycles-per-byte has also upgraded.
|
| |\ \
| | |
| | |
| | |
| | | |
Run "fixup-features" in preparation for release.
See merge request tpo/core/arti!3196
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The `TunnelId*` types will be reused in the relay reactor (exit relays
need to have the concept of a "tunnel ID" because of conflux).
Now the `relay::reactor` module only has a single import from `client`
(for the `unwrap_or_shutdown` helper, which we should be able to remove
soon). From now, we will avoid importing anything from `client` in the
`relay` module, and instead prefer refactoring the code as needed (to
pull the implementation-agnostic parts outside of `client`).
This commit has no functional changes, just code motion.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is just code motion (I suggest reviewing with `--color-moved`).
This also moves the implementation-agnostic parts from
`tor_proto::client::circuit` to a new `tor_proto::circuit` module.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
proto: Add a new RelayCircChanMsg message subclass.
See merge request tpo/core/arti!3198
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This will be used to restrict the types of messages that can be sent on
the relay-specific channels.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This enables us to remove the open-coded implementations in favor of the
derived version.
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
The code for generating these is repetitive (see `CreateResponse` and
`ClientChanMsg`), and we will soon need a `RelayChanMsg` type too, so
now is a good time to introduce a helper for generating the boilerplate.
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
tor-circmgr: Add more logging about timeout estimation.
See merge request tpo/core/arti!3152
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
We're seeing the logic that resets the timeouts when 18/20 connections
fail not triggering when we're expecting it to, this logging may help
figure out what's going on there.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-proto: Don't allow consecutive XOFF messages
See merge request tpo/core/arti!3197
|
| | | |/
| |/| |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
arti-rpcserver: Check IDs with a tag byte, not a magic length
See merge request tpo/core/arti!3191
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Edited-by: Nick Mathewson <[email protected]>
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Due to this, it is not possible to get a VPADDING before because it
requires a link protocol version to decideon the encoding:
https://gitlab.torproject.org/tpo/core/torspec/-/issues/366
Signed-off-by: David Goulet <[email protected]>
|
| |\ \
| | |
| | |
| | |
| | | |
Upgrade various dependencies in preparation for next release
See merge request tpo/core/arti!3188
|
| | | |
| | |
| | |
| | |
| | | |
Also, document why we are (for now) stuck using a tilde with our
ureq dependency.
|
| | | | |
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
tor-netdoc: parse2: Make field accumulator a nameable type
See merge request tpo/core/arti!3180
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
We're going to want to reuse this.
|
| | | |
| | |
| | |
| | | |
We're going to make this depend on $ftype differently.
|
| | | |
| | |
| | |
| | | |
This corrects the error message.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
The netstatus doc poc does test most of the functionality, but I want
some tests of edge cases that that misses.
|
| | | |
| | |
| | |
| | | |
Actually report the intro item, as the docs state.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-config-path: Fix another Windows warning
See merge request tpo/core/arti!3179
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Only Unix systems use the variable path_resolver.
Annotate it as unused for all other systems.
|