Automated testing of scripts that use GnuPG

Dashamir Hoxha dashohoxha at
Fri Mar 4 11:12:10 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.

>From your answer I understand that it has something to do with pinentry,
and I will search more on this direction.

By the way, Sharness is just a library of bash functions:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20160304/431ffdf9/attachment.html>

More information about the Gnupg-devel mailing list