python-gnupg uses "gpg --with-fingerprint --with-colons FILENAME" -- is this supported?
Werner Koch
wk at gnupg.org
Tue Oct 4 21:04:32 CEST 2016
On Tue, 4 Oct 2016 20:41, dkg at fifthhorseman.net said:
> * a bug in --fixed-list-mode in 1.4?
Yes.
> * an unsupported mode for programmatic use, since the behavior will
> vary depending on the contents of FILENAME (thus making it a bug that
> python-gnupg even tries to use this)?
It is not good to use this with unknown data because the default action
depends on the data. With 2.1 it is possible to use
--with-colons --always-trust \
--dry-run --import-options import-show --import
to list a key w/o changing any state. For an example see
gnupg/tools/gpg-wks-server.c
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 162 bytes
Desc: not available
URL: </pipermail/attachments/20161004/f8739a95/attachment.sig>
More information about the Gnupg-devel
mailing list