Importing a signed key

Bernhard Reiter bernhard at intevation.de
Fri Oct 22 16:20:59 CEST 2021


Hi Holger,

Am Freitag 15 Oktober 2021 17:55:28 schrieb Holger Sebert:
> The new version, however, does nothing:
>
>     $ gpg --import somekey.pub.key.gpg
>     gpg: Total number processed: 0

you could add more verbosity to find out what is going on, e.g. like
     gpg --verbose --import somekey.pub.key.gpg
or
     gpg --verbose --verbose --import somekey.pub.key.gpg
or 
     gpg --debug-level advanced --import somekey.pub.key.gpg

> On the other hand, importing the plain key-file ("somekey.pub.key")
> works:

If you want to check the signature, try
   gpg --verbose --verify somekey.pub.key.gpg
see if the result helps you.

Usually it is considered safe to import public keys, because they are not 
automatically trusted by GnuPG. (Usually means, unless you or some GnuPG 
using application is makeing other assumptions.)

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: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20211022/e2290869/attachment-0001.sig>


More information about the Gnupg-users mailing list