-----BEGIN PGP SIGNED MESSAGE-----
how I understood your issue: you have a key, changed it's passphrase and used
it successfully after that. Then, after some time, you could no longer use it
since GnuPG said you entered a "bad passphrase".
If that's correct, here are my thoughts:
- - There is no known passphrase mingling issue with GnuPG, so a passphrase you
once set should still work, but
- - It could be that you entered it with a different keyboard/lang/codepage
setting. If you have several locales installed (e.g. in Gnome), please
figure out which characters could be different.
- - Your key worked for some time and then no more after a while. That might be
due to gpg-agent that still had your key cached. After cache expiration, it
reasked for the passphrase.
- - To CREATE a rev cert, you need your secret key and your passphrase.
To IMPORT an existing rev cert, you don't need a passphrase. That is why
you should create a rev cert directly after generating a key pair.
- - If your broken key was uploaded on a keyserver and you cannot revoke, it
will stay "valid" there forever - just add a newer key and live with it.
If you successfully imported it, mind to upload the revoked public key.
The Enigmail Project - OpenPGP Email Security For Mozilla Applications
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Dies ist eine elektronische Signatur - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
Gnupg-users mailing list