| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |\
| |
| |
| |
| | |
shadow CI tweaks
See merge request tpo/core/arti!2989
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| | |
While useful, it significantly slows down the test. We should probably
just enable it when needed.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As per previous discussion there is some known flakiness around hidden
services with TestingTorNetwork enabled:
<https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1399#note_2921505>
Previously, only requiring 5 of 10 transfers to succeed has been enough
to keep this stable, but recently we've gotten unlucky and dipped under
this threshold: <https://gitlab.torproject.org/tpo/core/arti/-/issues/1986>
More investigation is warranted, especially wrt why the problem seems
to mostly be affecting articlient-onion-auth, but for now it's better to
have a low success threshold than to have folks overriding the CI
failure.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
ntor v3 is now always enabled.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This detected the account lifetime bugs fixed in this branch.
|
| | |
|
| | |
|
| |
|
|
| |
This tests that #1569 works.
|
| | |
|
| |
|
|
|
|
|
|
| |
Setting it for all arti processes causes a warning to be logged to
stderr, which causes the shadow ci script to fail.
It's enabled by default anyway when the feature is compiled in, so we
don't need to enable it explicitly.
|
| | |
|
| |
|
|
| |
This would have caught #1513 before it was merged.
|
| |
|
|
|
| |
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
|
| |
|
|
|
| |
Moving them to a separate variable makes the script more readable as we
add more hosts.
|
| |\
| |
| |
| |
| | |
Forbid script suffixes
See merge request tpo/core/arti!2153
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
| |
Some experimental features (i.e. `vanguards`) break the shadow
integration tests. Since the examples enable `experimental`, we need
`rust-latest` to build arti using `-p arti`, rather than from the
workspace level (because cargo does feature unification when building
the packages as a workspace).
|
| |
|
|
| |
Closes #1283
|
| |
|
|
| |
Closes #1202
|
| |
|
|
|
|
|
|
|
|
|
| |
The onion service keys now live in the `hss/<nickname>` subdirectory
within the keystore.
This layout change is **not** backwards-compatible, so if you want to
use your existing hidden service keys, you will need to manually move
them to `<keystore_root>/hss`.
Closes #1260
|
| |
|
|
|
|
|
| |
The role is a slug, and slugs are not allowed to contain uppercase
characters.
Closes #1195
|
| |
|
|
|
|
| |
We are about to replace `ArtiPathComponent` with `Slug`, but `Slug`s
don't support `.`, so let's strip the `.onion` suffix before encoding it
in the `ArtiPath`.
|
| | |
|
| |
|
|
|
| |
The algorithm name for x25519 keys has changed, so the test keys need to
be updated.
|
| |
|
|
|
| |
The algorithm name for expanded ed25519 keys has changed, so the test
keys need to be updated.
|
| |
|
|
|
|
|
| |
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 option is mostly a workaround for busy loops and other subtle race
conditions. While having it enabled can let us ignore some benign busy
loops and timing edge cases, it can also hide real problems; e.g.
burning extra CPU in a busy-loop.
https://shadow.github.io/docs/guide/limitations.html#busy-loops
|
| | |
|
| |
|
|
|
| |
This also adds a workaround - the arti service doesn't appear to
register itself (set up intro points) unless first used as a client.
|
| |
|
|
| |
This is to ensure a stable HS address.
|
| | |
|
| |
|
|
| |
socks_port is deprecated
|
| |
|
|
|
| |
Put one argument per line and use a yaml list instead of string (shadow
accepts either here).
|