| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
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
|