mirrors/arti.git/tests/shadow/shadow.data.template/hosts/fileserver-onion-auth, branch arti-v1.2.1mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.12023-12-14T18:21:38Zshadow test: Update the test client auth keys.2023-12-14T18:21:38ZGabriela Moldovangabi@torproject.org2023-12-14T17:37:47Zurn:sha1:c65a35fab5e6786f0be5c4645db7df054251514c
The algorithm name for x25519 keys has changed, so the test keys need to
be updated.
keymgr: 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
CI: Add client auth integration test.2023-07-12T15:36:11ZGabriela Moldovangabi@torproject.org2023-07-10T18:42:28Zurn:sha1:24501fdf0e4e4588b84d2ffd94e8288394ca7acd