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

2020-08-01 Thread Damian Johnson
> Isn't using "fingerprint" not a bit misleading since it is not the output of > a hash function but the ed25519 master public key itself? Hi nusenu, that's fair. We've begun to conflate a couple concepts here... * Relay operators, controllers, DirPorts, etc all require a canonical relay identifi

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

2020-08-01 Thread nusenu
> First, I'd advise that we call these 'v2 fingerprints' so it's clear > that we intend to substitute these anywhere traditional fingerprints > are used. Isn't using "fingerprint" not a bit misleading since it is not the output of a hash function but the ed25519 master public key itself? > Second

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

2020-08-01 Thread Damian Johnson
> The way I understand it is this: Relay fingerprints are based on the > RSA key, which will go away eventually. The canonical identifier will > be the identity. We should start that transition Thanks Sebastian. In that case we should put more thought into this because fingerprints are foundationa

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

2020-08-01 Thread Sebastian Hahn
Hi Damian, > On 2. Aug 2020, at 00:04, Damian Johnson wrote: > >> I'd like to use "ed25519 identity" or even just "identity" here going >> forward. > > Gotcha. The name of 'identity' makes me wonder how this relates to > relay fingerprints, which are the canonical identifier we use. > > Regardles

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

2020-08-01 Thread Damian Johnson
> I was wondering why the base64 string is 43 characters long for a 32byte > Ed25519 key. > 32*8/6=42 That is because tor drops trailing '=' from base64 encoded values within descriptors. Some fields indicate this within the spec, others don't. https://gitweb.torproject.org/stem.git/tree/stem/ut

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

2020-08-01 Thread nusenu
>> base64 encoding (parts of) the ed25519_master_id_public_key >> file, provides the same output as in master-key-ed25519 descriptor lines >> but I didn't find a spec for that key file to confirm the try and error >> approach >> or a tor command to simply output the ed25519_master_key public key i

Re: [tor-dev] IANA well-known URI suffix registration for tor-relay-fingerprints file

2020-08-01 Thread nusenu
I've put together the text, if you have any comments please let me know. I'm planning to submit it soon-ish. https://nusenu.github.io/tor-relay-well-known-uri-spec/ I'll also send it to the tor-relays mailing list. kind regards, nusenu -- https://mastodon.social/@nusenu signature.asc Descri

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

2020-08-01 Thread Nick Mathewson
On Sat, Aug 1, 2020 at 6:10 AM nusenu wrote: > > 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

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

2020-08-01 Thread nusenu
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 o