| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | | | | |
|
| | | | | | | |
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
proto: Consolidate all send_unbounded() calls in send_msg().
See merge request tpo/core/arti!3154
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This replaces a `send_unbounded()` call with `send_msg()`. Now
`send_msg()` is the only place where we call `send_unbounded()` in the
tunnel reactor, which makes it a bit easier to see which callsites have
the potential to cause buffering in the channel sink.
Prompted by #2112
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-rtmock: Slightly clean up CrateGetters macro
See merge request tpo/core/arti!3150
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
I want to use this as an example in a talk.
Add a blank line that makes it more readable, and generate only one
impl block with many methods.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
tor-cell: Fix comment in `ChannelCodec::encode`
See merge request tpo/core/arti!3155
|
| |/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This comment isn't correct if the encode() was given a non-empty buffer
(for example if two cells were written to the same buffer, the second
encode() would be given a non-empty buffer, so `pos != 5`).
|
| |\| | | | |
| |_|_|/ /
|/| | | |
| | | | |
| | | | | |
Update slab dependency to fix cargo audit
See merge request tpo/core/arti!3151
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Avoids
https://rustsec.org/advisories/RUSTSEC-2025-0047
I have considered whether this needs a TROVE. I think not.
We don't call the unsound method at all directly within arti.git.
As for our dependencies: I (with some flailing) managed to patch the
whole build to use a modified version of slab with the unsound method
sabotaged. This was successful. So I think nothing in our whole tree
uses it.
(I also verified that my sabotage arrangements were effective:
applying `#![cfg(any())]` at the top of slab's lib.rs did break the
build of hs.)
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
CI: tweaks to make chutney network bootstrap less noisy
See merge request tpo/core/arti!3149
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
