On Fri, Oct 30, 2015 at 06:34:22AM GMT, Antoine Jacoutot wrote:
> > but doesn't end up in the package itself.
>
> Fixed, thanks.
>
> > $ pkg_info -I pinentry
> > pinentry-0.9.6p1 PIN or passphrase entry dialog (ncurses interface)
> >
> > $ ls -l /usr/local/bin/pinentry*
> > lrwxr-xr-x 1 root wheel 15 Oct 28 21:44 /usr/local/bin/pinentry
> > -> pinentry-curses
> > -r-xr-xr-x 1 root bin 2844 Oct 25 14:35
> > /usr/local/bin/pinentry-curses
> >
> > $ file /usr/local/bin/pinentry*
> > /usr/local/bin/pinentry: symbolic link to
> > '/usr/local/bin/pinentry-curses'
> > /usr/local/bin/pinentry-curses: Bourne shell script text executable
> >
> > In the end, I had renamed the above two files and copied the built
> > binary in its place:
> >
> > $ ls -l /usr/local/bin/pinentry*
> > -r-xr-xr-x 1 root bin 2844 Oct 23 15:14 /usr/local/bin/pinentry
> > -rwxr-xr-x 1 root wheel 65760 Oct 30 01:06
> > /usr/local/bin/pinentry-curses
> > lrwxr-xr-x 1 root wheel 15 Oct 28 04:13
> > /usr/local/bin/pinentry.old -> pinentry-curses
> >
> > $ file /usr/local/bin/pinentry*
> > /usr/local/bin/pinentry: Bourne shell script text executable
> > /usr/local/bin/pinentry-curses: ELF 32-bit LSB shared object, Intel
> > 80386, version 1
> > /usr/local/bin/pinentry.old: symbolic link to
> > '/usr/local/bin/pinentry-curses'
> >
> > This, however, only "solves" the problem with the package but does *not*
> > resolve the issue which I had initially reported - pinentry doesn't
> > prompt for password, the terminal stays blank and pinentry-curses eats
> > up 100% CPU.
> >
> > Regards,
> >
> > Raf
> >
Hi Antoine,
Thanks for sorting that out. However, like I've mentioned in my last
paragraph - the main issue is still there.
I can recreate it on all 6 of my machines, i386 and amd64, physical and
virtual alike, with old or new GnuPG setup. I had just installed the
newest snapshot, built and installed pinentry-0.9.6p2.tgz package and
without ~/.gnupg directory, ran:
$ gpg2 --full-gen-key
and after answering the initial questions and confirming them,
pinentry-curses CPU usage climbs to 100%, while the console is blank,
the only thing that remains is the cursor in the top left corner of the
terminal - BTW, I had tested it over SSH, local console and X to no
avail.
I'm fairly convinced that pinentry, and not gpg2 or gpg-agent, is the
culprit here, because using gpg2 without it (with gpg-agent's pinentry
loopback mode), works just fine, i.e. with my existing GnuPG keys
putting 'allow-loopback-pinentry' into '~/.gnupg/gpg-agent.conf' and
using a passphrase file, the below command produces desired output:
gpg2 --pinentry-mode loopback --passphrase-file pass -d secret
Given the fact that this is a brand new install, no prior GnuPG cruft,
I'm pretty sure that it is not me ;^) but there indeed is an issue with
pinentry.
Regards,
Raf
