Hi Craig-- On Tue 2016-10-25 07:14:35 -0400, Craig Small <[email protected]> wrote: > Looks like you've hit the nail on the head there. > > *$ *dpkg -l 'pinentry*' > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Architecture Description > +++-==============-============-============-================================= > un pinentry <none> <none> (no description available) > un pinentry-curse <none> <none> (no description available) > un pinentry-doc <none> <none> (no description available) > ii pinentry-gnome 0.9.7-6 amd64 GNOME 3 PIN or pass-phrase entry > ii pinentry-gtk2 0.9.7-6 amd64 GTK+-2-based PIN or pass-phrase e > un pinentry-x11 <none> <none> (no description available) > *csmall**@**elmo**: **~**$ *readlink -f $(which pinentry) > /usr/bin/pinentry-gnome3 > > > I also rebuilt the pinentry-gnome3 with the patch. What happens now is I > get the ncurses pinentry screen appearing and the file is successfully > signed. So yes, for me at least your patch solves my problem. Thanks for > the quick answer!
Thanks for your followup! i don't know enough about your machine
("elmo") to understand the use case here -- given the installed pinentry
programs, is the computer you're ssh'ing into one that people use from a
graphical environment?
If not, maybe the easiest fix for you is to install pinentry-curses and
to purge pinentry-gtk2 and pinentry-gnome3.
If you personally also sometimes log into "elmo" graphically (with your
"csmall" account), that would also be useful information to know. In
that case, i think applying the patch to pinentry-gnome3 is the best
solution. that way you'd get the graphical pinentry when you have a
graphical session running, and you'd get the curses pinentry when the
session you're connected to is non-graphical.
does this make sense?
--dkg
signature.asc
Description: PGP signature
