| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Fix a comment about Result::flatten
See merge request tpo/core/arti!3138
|
| | | |
| | |
| | |
| | | |
Previously this API was nightly-only; now it's in 1.89.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Enable counter-galois onion negotiation and make it work.
See merge request tpo/core/arti!3133
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This change fixes a CGO bug: when extending circuits with ntorv3,
we were never actually using CGO encryption for the newly
constructed layer.
This change also simplifies the code a bit, by un-parameterizing
CircuitExtender a bit.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
(We can't negotiate the one without the other.)
|
| | | | |
| | | |
| | | |
| | | | |
Now that we can negotiate CC, we can negotiate CGO.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Update code for Edition 2024 (second attempt)
Closes #2101
See merge request tpo/core/arti!3137
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
`Future` is now in the prelude, so we don't have to give it an
explicit path.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
We're not sure why `cargo fix` did this, but it doesn't seem
necessary.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is now a reserved identifier. The automatic migration
changed it to a raw identifier (`r#gen`), but it's better to use a
different name.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The two main causes of errors were:
- Since some of the lifetime rules have changed, we no longer need
to do as many "bind a variable and immediately return it"
patterns, and so clippy now warns about them.
- We needed to adjust the explicit captures (`use<...>`)
in a couple of our RPIT instances.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
First, run
```
git grep -l "^edition =" |
xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```
Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.
Third, run cargo fmt again.
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
1. Run cargo fix --edition
2. Selectively revert the "if let"->"match" changes.
These changes are meant to protect us from the lifetime changes
for "if let" bindings in Rust 2024.
But we're not actually relying on the old lifetime rules
anywhere, and the match syntax here is quite ugly.
3. Automatically revert `$pat:expr_2021` to `$pat:expr`.
(We don't actually want to restrict the expression syntax
that our macros accept).
Done with
`git grep -l expr_2021 | xargs perl -i -pe 's/expr_2021/expr/g;'`
4. Run cargo fmt.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-protover: Small comment formatting fix
See merge request tpo/core/arti!3136
|
| | |/ /
| | |
| | |
| | |
| | | |
This breaks the syntax highlighting in vim for some reason and makes the
file unreadable for me.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
arti: keys: Fix incorrect display of CTor keystore entries in `keys list` CLI
See merge request tpo/core/arti!3116
|
| | | |
| | |
| | |
| | |
| | | |
* Update `display_entry` function to handle different `KeyPath` variants
* Add functions `display_arti_entry` and `display_ctor_entry`
|
| | | |
| | |
| | |
| | |
| | | |
(It is possible for arti-client to have flowctl-cc disabled, but for
tor-proto to have it enabled.)
|
| |/ /
| |
| |
| |
| | |
Since we now allow it to be turned on, we can include it among our
supported protocols.
|
| |\ \
| | |
| | |
| | |
| | | |
Resolve a few issues that had been waiting for an MSRV update.
See merge request tpo/core/arti!3129
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
I had been planning to use `[]::is_sorted` here, once we had
MSRV >= 1.82, but it turns out that we wanted strictly ascending
sequence, whereas `is_sorted` checks for a non-descreasing sequence.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Fix a few TODOs for PoW
See merge request tpo/core/arti!3106
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
These now `warn!` and cleanly exit their respective threads on error,
instead of panicking.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This just pushes around where the panic is for now, but enables better
handling of this error, and it makes it clearer that this panic will
only stop this thread.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The "a few KB" measurement was done by using the get_size crate to
measure the size of the RendRequest object, but due to limitations in
that crate (and in my willingness to go implement ways of checking the
size of external types), it might be somewhat off. The ~32MB value is
based on the idea that each RendRequest is 4KB.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This adds the three new parameters specified in Prop 362 [0].
Two of these replace hardcoded defaults in the code.
The third, HiddenServiceProofOfWorkV1ServiceIntroTimeoutSeconds, is not
implemented yet, but will be in a future commit.
[0]: https://spec.torproject.org/proposals/362-update-pow-control-loop.html
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Bump MSRV to Rust 1.85
Closes #2095
See merge request tpo/core/arti!3128
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
(We were unable to do this before, since it required a rust version
we didn't have.)
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Remove semver.md files, post-release.
See merge request tpo/core/arti!3127
|
