Re: Best way to get fingerprint programatically

2019-12-19 Thread Werner Koch via Gnupg-users
On Wed, 18 Dec 2019 11:51, john doe said:
> By any chance, could something like the following be implemented?:
>
> $ gpg -K --print-fingerprint-only test

I doubt that this helps because the only way to get a single result is
to use the fingerprint for .  Thus a second info item would be
required to show the user-id matching the fingerprint - et voila we are
back to --with-colon listing parsing.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: "--refresh-keys" not working.

2019-12-19 Thread Werner Koch via Gnupg-users
On Wed, 18 Dec 2019 09:51, Gerard E. Seibert said:

> gpg: mpi too large (28876 bits)
> gpg: read_block: read error: Invalid packet

One of the keys you imported is corrupt and thus rejected.  The debug
flags don't help here, it would be better to enable --verbose so that
you can see which key was rejected or at least which was the last key
which refrshed fie.  If you don't get any further, you should add

log-file /somewhere/dirmngr.log
verbose
debug ipc

to ~/.dirmngr.conf, kill dirmngr and retry.  The log will receive all
requests from gpg to load the keys from some keyserver.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users