GNU bug report logs - #23619
Some epg tests fail

Previous Next

Full log

View this message in rfc822 format

From: npostavs <at> users.sourceforge.net
To: Daiki Ueno <ueno <at> gnu.org>
Cc: 23619 <at> debbugs.gnu.org, Glenn Morris <rgm <at> gnu.org>
Subject: bug#23619: Some epg tests fail
Date: Mon, 20 Feb 2017 13:16:37 -0500

Daiki Ueno <ueno <at> gnu.org> writes:

> npostavs <at> users.sourceforge.net writes:
>
>> Although this doesn't solve the problem for gpg 2.0.
>
> For a proper fix, you might want to check how GPGME and its test suites
> do.

I don't see anything to handle gpg 2.0, specifically.  They do disable
pinentry for versions below 2.1.  Maybe their tests don't work with 2.0
either?

>> I think we could use '--batch' with '--passphrase' or 'passphrase-fd'
>> for this, although neither of these works as a callback.
>
> If that approach makes all interactions with gpg synchronous, it
> wouldn't be acceptable.

With '--passphrase-fd', interactions remain asynchronous from Emacs'
point of view, but gpg sends no output until receiving the passphrase on
the given fd, so the normal callback doesn't get triggered.  So to make
that work, we would have to send the callback's output immediately after
starting the gpg process.

Using '--passphrase' means giving the passphrase on the command line,
which is not very good in terms of security for normal use, though
acceptable for tests.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.