[email protected] (Antoine Jacoutot), 2015.10.28 (Wed) 06:39 (CET):
> 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.
OpenBSD 5.8-current (GENERIC.MP) #1394: Tue Sep 29 20:42:18 MDT 2015
[email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
gpgme-1.5.1p1 libassuan-2.1.1 libgpg-error-1.20 mutt-1.5.24p0v0-gpgme
It might be the same thing that is bugging me for quite some time - just
not enough to report.
Occasionally I have similiar symptoms with mutt+gpgme.
Just found a way to reproduce:
in mutt, make new message, tell mutt you want to sign/crypt, send -
pinentry asks for passphrase. hit ctrl-c now and you have an orphaned
'pinentry --display :0 (pinentry-curses)'
Most of the time it eats lots of cpu but not always (at least two
occasions). Sometimes there's something that looks like a blank xterm
window.
After ctrl-c mutt prompts are broken, too. Lots of asterisks ('*') when
you type text. Not even easy to get out of mutt correctly at that point.
> > 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
I'm a bit behind:
$ file /usr/local/bin/pinentry*
/usr/local/bin/pinentry: symbolic link to
'/usr/local/bin/pinentry-curses'
/usr/local/bin/pinentry-curses: ELF 64-bit LSB shared object,
x86-64, version 1
> > 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.
Will try to find time to get me onto real -current.
Bye and thanks for looking at it, Marcus
> !DSPAM:56306053111941282615443!
