On Wed, Oct 28, 2015 at 04:35:14AM +0000, Raf Czlonka wrote:
> On Sat, Oct 24, 2015 at 08:59:48AM BST, Antoine Jacoutot wrote:
> > > > Hi Antoine,
> > > >
> > > > On a (somewhat), related note - since the last (so it seems) update to
> > > > pinentry, it doesn't prompt for pass{word,phrase} any more, i.e.
> > > >
> > > > gpg2 -d file.gpg
> > > >
> > > > starts gpg-agent, which in turn starts pinentry, all I can see is
> > > > blank tty and after a couple of seconds, pinentry runs at 99% CPU:
> > > >
> > > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME
> > > > COMMAND
> > > > rjc 20819 99.0 0.1 1996 5392 ?? R 6:41AM 1:25.35
> > > > pinentry (pinentry-curses)
> > >
> > > Hmm that's odd... my initial tests did work.
> > > I'll have a look this week-end, thanks for the report.
> >
> > Can you wait for and try the new ports snapshot when it is there.
> > I cannot reproduce your issue, pinentry works just fine here.
>
> Hi Antoine,
>
> The newest i386 package (new amd64 ones haven't been built yet so can't
> verify) does something really strange:
>
> $ 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
>
> So, the pinentry is still a symbolic link instead of the intended
> wrapper script and pinentry-curses is the actual wrapper -
> pinentry-curses (the binary) is not even a part of the package.
The pkg snapshot is too old I guess.
--
Antoine
