Wow. Thanks very much for such a detailed reply. GPG can be counter-intuitive
at times, but it seems there is always a way. Shalom!
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Tuesday, August 27, 2019 6:30 PM, Werner Koch wrote:
> On Tue, 27 Aug 2019 00:18, gnupg-us
I've been working on a scheme for signing binary images that we ship out to
various remote systems. The remote system expects the file to be both encrypted
and signed, but there seem to be some corner cases:
(1) If a file is signed but the signature is incorrect, 'gpg2 -d' returns a
non-zero st
Well, on second thought, I think what I will try to do today is restructure
everything so I can use a single GNUPGHOME. If that works out then we'd
probably be in a better position to take advantage of the new design you're
working on. By the way, could you describe that in more detail? What new
Thanks for that. Given that I need to do multiple operations on the card with
different GNUPGHOME values during one session, is there a way to cause an
earlier instance of scdaemon to either exit or to release the card, so that a
new instance can have exclusive access? It seems like this would h
Regarding this, more significant than the Key parameter to gpgme_op_interact()
in the two example that I gave being different may be the fact that the home
directory set for the underlying gpgme_ctx_t (via the home_dir argument to
gpgme_ctx_set_engine_info()) is different. In the case of the --e
Hello,
I'm building an application that configures smart cards (currently Yubikeys) as
OpenPGP cards using GPGME and the gpgme_op_interact() API. In order to provide
the functions needed at the user level, I need to engage in several different
interactions, most notably some that emulate --card-
