[Gpg4win-users-en] short-id <-> long-id (Re: gpg4win 3.1.16 with updated GnuPG 2.2.32: No public key found despite having refreshed the keys)

[Bernhard Reiter]

Hi Stella,

checking it today I was not paying attention and need to correct myself:

Am Dienstag 21 Dezember 2021 20:40:33 schrieb Stella Ashburne:
> > it has the "short-id" "E53D989A9E2D47BF".

This, of course, is already the long-id.
The short id would have been the right half of it: "9E2D47BF".

What I do often is to use the full fingerprint.

> User name: Tor Browser Developers (signing key) <torbrowser at torproject.org>
> Fingerprint: EF6E 286D DA85 EA2A 4BA7  DE68 4E2C 6E87 9329 8290

> What's a long key id? What does its format look like?

The short and long forms are from the end of the fingerprint.
Some pubkey servers need an "0x" in front and no whitespace to recognise it.

For details see
https://gnupg.org/documentation/manuals/gnupg/Specify-a-User-ID.html

"The best way to specify a key Id is by using the fingerprint. This avoids any 
ambiguities in case that there are duplicated key IDs."

Sorry for the initial confusion. :/

Best Regards,
Bernhard

-- 
www.intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.wald.intevation.org/pipermail/gpg4win-users-en/attachments/20211222/249cacb9/attachment.sig>