On 11/06/2016 07:19 AM, Jörg-Volker Peetz wrote:
I'm using pinentry-gtk2 which also works in text-mode.
KDE users may prefer pinentry-qt or pinentry-qt4 which also works in text-mode.
Regards,
jvp.
Frank, JVP,
Thanks for the info. This completed the solution for me. Based on your
info and s
I'm using pinentry-gtk2 which also works in text-mode.
KDE users may prefer pinentry-qt or pinentry-qt4 which also works in text-mode.
Regards,
jvp.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Nov 06, 2016 at 07:42:40AM +0100, Frank wrote:
> Op 06-11-16 om 04:52 schreef H.S.:
> >So, how do I tell gpg to work on std in when on a terminal instead of
> >relying on a graphical session?
>
> The man page for gpg-agent suggests you can set
Op 06-11-16 om 04:52 schreef H.S.:
So, how do I tell gpg to work on std in when on a terminal instead of
relying on a graphical session?
The man page for gpg-agent suggests you can set that with the
--pinentry-program option. I haven't tried this myself, but adding
something like
pinentry-p
On 11/05/2016 05:50 PM, Frank wrote:
Op 05-11-16 om 21:23 schreef H.S.:
Still, however, decryption my file using gpg2 does not work: it does not
ask for my passphrase on the std in and just times out. gpg1 works
though.
What am I missing?
Package I have on my testing box:
$ COLUMNS=75 dpkg -l
Op 05-11-16 om 21:23 schreef H.S.:
Still, however, decryption my file using gpg2 does not work: it does not
ask for my passphrase on the std in and just times out. gpg1 works though.
What am I missing?
Package I have on my testing box:
$ COLUMNS=75 dpkg -l gnupg* | grep ^i
ii gnupg 2.
On 11/05/2016 02:53 AM, Frank wrote:
Op 05-11-16 om 03:55 schreef H.S.:
I upgraded my testing box last night and now my gpg decryption does not
work anymore.
gpg2 can't find your secret keys because it stores them elsewhere. For
gpg1 they are in the secring.gpg file and gpg2 looks at the file
Op 05-11-16 om 03:55 schreef H.S.:
I upgraded my testing box last night and now my gpg decryption does not
work anymore.
Until a couple of months ago, gpg was gpg1. It's gpg2 now and you need
to specify gpg1 explicitely if you want to use the 'classic' version.
You may have to install the gnu
I upgraded my testing box last night and now my gpg decryption does not
work anymore.
I have a file encrypted for myself which I have been using. Till
recently I was able to decrypt it successfully for years.
After last night's upgrade, I get the following:
$> gpg -d somefile.txt.asc
gpg: e
9 matches
Mail list logo
