mirrors/arti.git/tests/shadow, branch arti-v1.1.8mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.82023-08-16T09:43:28Zkeymgr: Do not expect x25519 keys to be stored as ed25519 ssh keys.2023-08-16T09:43:28ZGabriela Moldovangabi@torproject.org2023-07-25T10:51:34Zurn:sha1:17d965e8941397b8c362d88df8c90e6a2632bd52
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 `"x25519@torproject.org"`).
Closes #936
[custom algorithm names]: https://github.com/RustCrypto/SSH/pull/136
arti-client: Use the config struct from tor-keymgr.2023-07-13T11:29:57ZGabriela Moldovangabi@torproject.org2023-07-12T18:07:55Zurn:sha1:0260405603c41ae88486996868ee1ebe2fa8615aCI: Reduce the success threshold for the HS client integration tests.2023-07-12T16:11:56ZGabriela Moldovangabi@torproject.org2023-07-12T15:42:59Zurn:sha1:d684073a31bba2685c74758dad978eb7121bbd3e
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1399#note_2921505
CI: Add client auth integration test.2023-07-12T15:36:11ZGabriela Moldovangabi@torproject.org2023-07-10T18:42:28Zurn:sha1:24501fdf0e4e4588b84d2ffd94e8288394ca7acdarticlient-onion: don't filter onion addresses2023-07-03T19:15:23ZJim Newsomejnewsome@torproject.org2023-07-03T17:59:24Zurn:sha1:3eda3a7936ab8cbaefd2f89bd33f920b0e2bcf09Dedupe arti configs and match TestingTorNetworks HS config2023-07-03T19:15:23ZJim Newsomejnewsome@torproject.org2023-07-03T17:04:15Zurn:sha1:3b01f3ba61549b5a769cf8fbc46afc449da595d7shadow test: disable trace-level logging2023-07-03T17:49:14ZJim Newsomejnewsome@torproject.org2023-06-26T19:42:40Zurn:sha1:2b895f4de3c31e1e2bbbbb7c61adf3839016d61e
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.
shadow test: disable worker spinning2023-07-03T17:49:14ZJim Newsomejnewsome@torproject.org2023-06-26T19:41:41Zurn:sha1:5755add5e066f77c9caf3631c3db31da45694e50
This optimization doesn't seem to help much for this test; disable it to
avoid burning CI runner CPU.
shadow test: enable arti's `log_sensitive_information` option2023-07-03T17:49:14ZJim Newsomejnewsome@torproject.org2023-06-22T22:24:47Zurn:sha1:3dc90f03ecf3b8fca5769eac5443ef836df0c7dfshadow test: fix hidden service dir permissions2023-07-03T17:49:14ZJim Newsomejnewsome@torproject.org2023-06-22T21:55:29Zurn:sha1:e773d2c44a4218eb516d2915c670408fb74c3153