[tor-dev] How do Ed25519 relay IDs look like?

[nusenu]

> The only question that came up was: Will there be two types of relay fingerprints
> in the future (Ed25519)?

I assume the correct proposal for the Ed25519 keys is this:
https://gitweb.torproject.org/torspec.git/tree/proposals/220-ecc-id-keys.txt

I'm wondering what kind of format is used for a relay's Ed25519 ID in tor?

The spec says base64:

>    When an ed25519 signature is present, there MAY be a "master-key-ed25519"
>    element containing the base64 encoded ed25519 master key as a single
>    argument.  If it is present, it MUST match the identity key in
>    the certificate.

examples:
grep master-key-ed 2020-07-28-19-05-00-server-descriptors |head -2

master-key-ed25519 clT/2GWmTY/qU5TBGaudAIjOUUxUdKhMY/Q5riK6G2E
master-key-ed25519 qDI9PbwtiKzpR9phLnWI99uimdwNW8+l9c7hDoWV9dQ

Is this the canonical format you use when referring to a relay's Ed25519 identity?

(So it is not a hash of the key but the entire public Ed25519 master key of the relay since Ed25519 keys are so short.)

What command does a relay operator need to run to find out
his relay's Ed25519 ID on the command line?

Here is the example for the RSA1024 SHA1 fingerprint:
openssl rsa -in keys/secret_id_key -outform DER -RSAPublicKey_out 2> /dev/null| openssl sha1 -r|cut -d" " -f1|sed -e 's/ /,/g'

also:
Are there any plans to include the Ed25519 IDs in onionoo/Relay Search?
What format would you most likely use there?

thanks,
nusenu


These are the filenames I would suggest for the well-known registry:
tor-relay-rsa-fingerprints
tor-relay-ed25519-pubkeys



-- 
https://mastodon.social/@nusenu

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20200731/ffbc602c/attachment.sig>