| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
This is the transfer size used in the tor CI chutney tests, to
more-fully exercise SENDMEs / congestion control.
We also increase the simulation run time to allow time for the larger
transfers.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is in preparation to switch arti's console logging to use stderr
instead of stdout. The test script currently fails the test if there are
non-empty stderr files, since that's where rust panics end up getting
recorded.
It will also make it easier to see if there is any other non-logging
output.
Also disable trace-level logging for the tor_proto module. It's unclear
exactly when/why this was added, but it's probably overkill other than
when debugging.
|
| |
|
|
|
|
|
|
|
|
|
| |
Not expected to solve any immediate issue, but helpful for consistency
with the chutney-shadow CI, and I think in the past we've hit busy-loop
deadlock without it if/when we try increasing the simulation end time.
Similarly, we apply the same tuning of "max_unapplied_cpu_latency" as we
use in the chutney-shadow simulation, which gets back some of the
simulation stability that enabling model-unblocked-syscall-latency
otherwise sometimes sacrifices.
|
| |
|
|
|
|
|
|
|
|
| |
The pcaps are only used to check for leaks by reading the packet
source/destination, so we don't need the entire packet. This should make
CI artifacts a bit smaller.
The fixed-size portion of an IP header is 20 bytes for IPv4 and 40 bytes
for IPv6. Shadow doesn't support IPv6, but used the IPv6 header size
anyways.
|
| | |
|
| | |
|
| |
|
|
| |
This tests that #1569 works.
|
| | |
|
| |
|
|
|
| |
This tests that the client configured in the `authorized_clients`
directory of the service is able to connect.
|
| |
|
|
|
| |
This will be used with the new `fileserver-onion-arti-auth` test hidden
service.
|
| |
|
|
|
|
|
|
|
| |
This adds a new restricted discovery hidden service
(`fpqqmiwzqiv63jczrshh4qcmlxw6gujcai3arobq23wikt7hk7ojadid.onion`)
that has 2 authorized clients:
* `alice`, the client configured in the `restricted_discovery.static`
list in its TOML config
* `default`, the client configured in `authorized_clients/default.auth`
|
| |
|
|
|
|
| |
We don't need this now that #1417 is fixed.
This reverts commit a9010f6300c25e4602ecf8017ca176c724ecdfa5.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Without this change, one of the tgen processes doesn't exit as expected:
```
618990:00:06:50.991981 [4717:shadow-worker] 00:30:00.000000000 [ERROR] [torclient-onion-artiserver:11.0.0.19] [process.rs:1525] [shadow_rs::host::process] process 'torclient-onion-artiserver.tgen.1001' exited with status StoppedByShadow; expected end state was exited: 0 but was running
```
This is because of a stub circuit selection bug that only manifests when
the `torclient-onion-artiserver` and
`torclient-onion-artiserver-full-vanguards` tests are run at the same
time.
See #1417 for more details.
|
| |
|
|
|
|
|
| |
This adds an onion service that uses full vanguards, and a client
that connects to it.
Closes #1408
|
| |
|
|
|
|
|
| |
Disabling the shadow option --model-unblocked-syscall-latency causes
this bug not to surface. Better to remove this workaround for now
so that we can revisit again if/when it does rather than continue to
mask it.
|
| | |
|
| |
|
|
|
| |
This also adds a workaround - the arti service doesn't appear to
register itself (set up intro points) unless first used as a client.
|
| | |
|
| |
|
|
| |
socks_port is deprecated
|
| |
|
|
|
| |
Put one argument per line and use a yaml list instead of string (shadow
accepts either here).
|
| |
|
|
|
|
|
|
|
|
|
| |
The arti-extra binary has several experimental features enabled.
Currently it is used to test experimental onion service features, but it
would be useful also do a test of the arti-extra binary in the same
configuration and workload as the arti binary (which has the default
featureset).
In a follow-up commit, we'll enable the experimental ntor-v3 handshake
implementation in the arti-extra binary.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Some hosts were configured to log at trace level instead of the global
default (debug level). This was resulting in quite large shadow log
output.
|
| |
|
|
|
| |
Without this, the onion client was failing to find a guard.
We recently made this change in shadow's "tor minimal" test as well.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
As of shadow 2.3, shadow can locate executables from the PATH, letting
us avoid hard-coded paths here.
|
| | |
|
| | |
|
| |
|
|
|
| |
This was a temporary stop-gap to work around a busy loop that seemed to
happen before. I am no longer able to reproduce any such problem.
|
|
|
Fixes https://gitlab.torproject.org/tpo/core/arti/-/issues/174
|