On 03/01/14 14:31, Dan Mahoney, System Admin wrote:
> Hauke, in your posts, you mention that the pinentry protocol isn't on the GPG
> website. Could that please be fixed by the people who maintain the project?
> I
> notice it also missing from http://www.gnupg.org/documentation/manuals/
I remem
On Fri, 3 Jan 2014, Hauke Laging wrote:
Am Fr 03.01.2014, 01:14:22 schrieb Dan Mahoney, System Admin:
It basically works perfectly with gpg1, where I can get an inline
prompt for a password, but gpg2 falls short where it tries to set up
some kind of a unix-socket connection to a pinentry dialo
On Fri, 3 Jan 2014, Hauke Laging wrote:
Am Fr 03.01.2014, 01:14:22 schrieb Dan Mahoney, System Admin:
It basically works perfectly with gpg1, where I can get an inline
prompt for a password, but gpg2 falls short where it tries to set up
some kind of a unix-socket connection to a pinentry dialo
Am Fr 03.01.2014, 01:14:22 schrieb Dan Mahoney, System Admin:
> It basically works perfectly with gpg1, where I can get an inline
> prompt for a password, but gpg2 falls short where it tries to set up
> some kind of a unix-socket connection to a pinentry dialog, and this
> all falls apart within t
All,
I have a script that I use to send mail (as part of pine/alpine) that
needs to prompt for my key passphrase.
I run alpine on a private unix server, within a screen session.
It basically works perfectly with gpg1, where I can get an inline prompt
for a password, but gpg2 falls short wher