| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In particular, this is to avoid floods of:
> compute_drain_rate(): Bug: Computing stream drain rate with zero time delta
in tor logs.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
arti isn't trying to use conflux yet, but the tor nodes are. Things
were stumbling along without this, but adding it reduces some log noise,
and might help with consistency.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reduces some noise and warnings, and may help with consistency.
e.g. this avoids everything trying to repeatedly contact the directory
authorities before they're up.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In this commit there should be little effective difference, other than
combining the "setup", "configure", and "wait_for_bootstrap" steps.
"chutney bootstrap" also support multi-phase networks, though, in which
chutney waits for some nodes to fully bootstrap before bringing up other
nodes.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is the time we wait for the network to bootstrap before giving up.
With the larger network we seem to need this extra time.
We've already increased the default in chutney to 300; no reason to use
a smaller value here.
Keep the explicit-setting for now as a convenience in case we want to
modify it again.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Primarily to get arti hidden services support, added in
tpo/core/chutney!77
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
arti: keys: Fix `display_keystore_entries` output
See merge request tpo/core/arti!3143
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
arti-crate-readme-typos: Typos
See merge request tpo/core/arti!3115
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
- "command-line" should be written with hyphen when adjective.
- Rephrased some sentences.
- OS X is now called MacOS.
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
doc/dev/notes: relay-reactor: Add a relay reactor implementation sketch.
See merge request tpo/core/arti!3146
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This is a rough sketch for the new relay tunnel reactor design.
It also contains a proposed refactoring which would enable us to
repurpose much of the existing tunnel reactor implementation.
This is by no means final, and we might choose not to refactor the
tunnel reactor until after we have an initial working (or quasi-working)
version for the relay reactor.
|
| |\ \ \ \ \ \ \ \
| |_|_|_|/ / / /
|/| | | | | | |
| | | | | | | |
| | | | | | | | |
circmgr: Don't count channel negotiation towards circuit built time.
See merge request tpo/core/arti!3141
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This is important, since some circuits require us to negotiate a new
channel, and some don't: by adding this variability, we can easily
learn a timeout based on pre-existing channels to our guards, but
then later time out if it takes a while to open a TLS connection.
This is a possible solution to part of #2079, a bug where we "learn"
a circuit timeout that is too low for us to satisfy.
|
| | | |_|/ / / /
| |/| | | | | |
|
| |\ \ \ \ \ \ \
| |_|_|_|/ / /
|/| | | | | |
| | | | | | |
| | | | | | | |
web: Small fixes/improvements
See merge request tpo/core/arti!3109
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This is the tor project onion address returned from:
```
curl --head https://www.torproject.org
```
I think it's better to give an example with our own onion service than a
third-party one. Also ddg seems to use an obfuscated webpage with a single
line, which doesn't show nicely in the terminal.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
No one is actively updating the web docs, so the existing comment is
misleading.
|
| |/ / / / / / |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
arti-client example: Write rather than hide an elided lifetime
See merge request tpo/core/arti!3145
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes this warning. Not sure why it's not showing up in CI.
--> crates/arti-client/examples/one_hop_circuit.rs:16:35
|
16 | fn find_one_hop_dir_cache(netdir: &NetDir) -> Option<Relay> {
| ^^^^^^^ ----- the same lifetime is hidden here
| |
| the lifetime is elided here
|
= help: the same lifetime is referred to in inconsistent ways, making the signature confusing
= note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
help: use `'_` for type paths
|
16 | fn find_one_hop_dir_cache(netdir: &NetDir) -> Option<Relay<'_>> {
| ++++
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
hyper-examples: Update examples for `hyper`.
See merge request tpo/core/arti!2941
|
| | | | | | | |
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
examples/hyper/hyper-http-client-example/Cargo.toml
examples/hyper/hyper-http-hs-example/Cargo.toml
In both cases, just the change of edition, which I have applied to
examples/hyper-examples/Cargo.toml
instead.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
tor-proto: Use error report in tunnel/channel reactor mainloop
Closes #2057
See merge request tpo/core/arti!3122
|
| |/ / / / / / |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
tor-proto: Fix failing cargo fmt
See merge request tpo/core/arti!3140
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
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.
|
| |\ \ \ \ \ \ \ \ \
| |_|_|/ / / / / /
|/| | | | | | | |
| | | | | | | | |
| | | | | | | | | |
doc: dev: notes: Add keys-integrity-check.md
See merge request tpo/core/arti!3126
|
| | | | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
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.
|
