| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
The secret keys are prefixed with `KS`, not `KP`.
|
| |
|
|
| |
The privateness of the keys is encoded in their name.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the Arti key store would store x25519 secret keys as ed25519
OpenSSH keys, which it would convert to x25519 upon loading (using the
conversion function added in !1297 (merged)). This approach isn't good
enough though: most people will probably want to bring their existing
x25519 keys, and in order to store those in OpenSSH format, we'd need
convert them to ed25519, which is impossible (because the secret part of
an x25519 key contains a SHA512'd secret, whereas the corresponding,
"un-expanded", ed25519 secret key contains the secret itself rather than
the SHA).
Now that `ssh-key` has support for ssh keys with [custom algorithm
names], we can store x25519 in OpenSSH format directly. This commit
changes the storage format used by the keymgr for x25519 client auth
keys (from ed25519-ssh to our own custom key type with an algorithm name
of `"[email protected]"`).
Closes #936
[custom algorithm names]: https://github.com/RustCrypto/SSH/pull/136
|
| | |
|
| |
|
|
| |
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1399#note_2921505
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
This optimization doesn't seem to help much for this test; disable it to
avoid burning CI runner CPU.
|
| | |
|
| | |
|
| |
|
|
|
| |
Without this, the onion client was failing to find a guard.
We recently made this change in shadow's "tor minimal" test as well.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This commit changes the shebang in all shell scripts from absolute
paths (such as `/bin/bash` or `/usr/bin/python3`) to the `/usr/bin/env`
binary with the accompanying interpreter as it's argument.
The reason for this are as follows:
- NixOS cannot work with absolute paths
- BSD systems install their packages in /usr/local/bin
|
| |
|
|
|
| |
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
|