Automated testing of scripts that use GnuPG

Dashamir Hoxha dashohoxha at
Tue Mar 15 04:27:40 CET 2016

On Fri, Mar 4, 2016 at 10:18 AM, Andreas Stieger <astieger at> wrote:

> Hi,
> On 03/04/2016 07:48 AM, Dashamir Hoxha wrote:
> > [...] develop some wrapper shell scripts [...]
> > But I am having problems because `gpg` has a "nasty" behaviour, it
> > always pops up a window for getting the passphrase. Maybe this is a nice
> > feature for the normal operation of the scripts, but for automatic
> > testing it breaks the 'automatic' part.
> You may want to use a configuration that causes GnuPG to use different
> pinentry flavour that works in your test rig: the tty one, or a mock
> implementation of the simple pinentry protocol, possibly written in
> Sharness itself if it can do IPC.

FYI, a mock implementation of the pinentry protocol could be a solution,
like this one:

But for automatic testing purposes I find that using keys without a
passphrase is a better solution (no passphrase, no pinentry needed). Why
did I not think about this earlier?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20160315/e7a802f4/attachment-0001.html>

More information about the Gnupg-devel mailing list