-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > 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. Murphy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iJwEAQECAAYFAlQfLbMACgkQUVKxkWZz2Q25uQP9GgJikeZPNYVBYQ2Gkzr4OP7r jFMhyQyfeut5RWgx6CPovH13nJXXR2tOnJnzkCAimZr07rIZh2WQbCKF8r5cFWFs yJGG2/en9xUeZiDOzvMT5oJ6WJdHJNJzf4hLZGF4pEzgHYC596z9L9u28S7dBRws f3rAdWupaWmKSuyXB6o= =0o7W -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users