mac3iii at gmail.com
Sun Sep 21 21:57:39 CEST 2014
-----BEGIN PGP SIGNED MESSAGE-----
> What are the symptoms of gnome highjacking pinentry ?
Phillip, if you are encrypting/decrypting or signing emails with gpg2
and having no problems with error messages then you don't need to put
in the command of step no. 2. The symptoms of a hijacking is that
when gpg2 tries to put up a pinentry box gnome keyring hijacks the
process and puts up its own box. Recent versions of gnupg-2.0.x will
then display an error message in the terminal and bad things happen.
Either you only get one attempt at changing passphrases or the whole
process crashes. The process may succeed or not, it is unpredictable.
If you wish to witness it first hand I recommend using virtualbox.
Set up a fresh install of Ubuntu inside virtualbox (really easy and
fun) and then install Gnupg-2.1.0 without the command in step 2. Then
try to generate a key, if you can. The virtualbox environment is
perfect for experimenting with new beta versions and playing with ECC
keys and subkeys, without disturbing you regular production environment.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----
More information about the Gnupg-users