excuse me sirs. when i wrote that question i was already very tired.
so in the meantime i realized that there are different code paths for
ed/x448 goldilocks.
one of them distinguishes the Endiannes on behalf of the algorithm (e.g.
sets is_little_endian to true | false in g10/ecdh.c).
i haven't
you are absolutely right:
when explicitly telling GnuPG to display x448 fingerprints (gpg
--fingerprint) it just spits out the "abbreviated hex format" by takes
the first 50 bytes and sweeping the rest under the rug! Not very nice.
Likewise by telling GnuPG you really want the short keyID
hi.
i scrutinized the new, announcements, mailinglist history and the ietf
drafts but still couldn't find out the reason for following observation.
let's say we have an ed25519 key with the 40 hex character fingerprint of
then its long keyid is
her wrote:
>
> On 28 Mar 2024, at 12:54, Christian Sommer via Gnupg-users
> wrote:
>
>
> when explicitly telling GnuPG to display x448 fingerprints (gpg
> --fingerprint) it just spits out the "abbreviated hex format" by takes
> the first 50 bytes and sweeping the
