I doubt gpg2 is correctly set up on your PC, since you're not prompted for a password.
Please follow this guide to ensure it's working properly: https://enigmail.net/support/gnupg2_issues.php Patrick ----- Original Message ----- From: "Lars Noodén" <[email protected]> Sent: 02.09.2015 - 21:30 To: Enigmail user discussion list <[email protected]> Subject: Re: [Enigmail] New enigmail tries to decrypt with outdated, disabled key > On 09/02/2015 10:13 PM, Ludwig Hügelschäfer wrote: >> On 02.09.15 20:24, Lars Noodén wrote: >> >>> The error message between the message body and the headers is : >>> >>> Enigmail Error - decryption failed; click on 'Details' >>> button for more information. >> >> Is this a message sent from you or sent from another person? What >> happens, if you re-enable your old key? Disabling of an old key is not a >> good idea if you want to decrypt stuff which is encrypted using this key. > > If I send and if others send, it is encrypted using the new key. It's > looking more like Enigmail is trying to decrypt using the wrong key, so > the subject . > >>> When I click on Details and choose View Key Properties I get shown >>> Primary User ID, Key ID, and Fingerprint which are for the wrong key. >> >> Well, as said: You must use the key for which this message has once been >> encrypted to. If it is disabled, it cannot be used and you get an error >> message. > > The key it is showing in the error message is the active key. > >>> If I try to sign an outgoing message, I get this: >>> >>> Key 0xXXXXXXXX not found or not valid. The (sub-)key >>> might have expired. >>> >>> If I go into Engimail -> Key Management -> Key properties for that key, >>> it shows that the key is valid and expires next year. >> >> Do you get prompted for the passphrase or does the error prompt happen >> before? > > Before. No passphrase gets asked. > >> [gpg.conf] >> >>> gpg.conf is stock, I haven't changed it. Here are the active lines: >>> >>> $ egrep -v "^#|^$" gpg.conf >>> keyserver hkp://subkeys.pgp.net >>> use-agent >>> >>> default-key FE35B305 >> ^^^^^^^^ >> Is this the keyId of your old (disabled) or of your new key? Does the >> undesired behaviour go away if you comment out this line (put a # at the >> first column)? > > Neither. That is yet another key, an old one but not as old. I guess I > should say I did not change gpg.conf manually before. Changing that > line to the new key and restarting Thunderbird has no noticeable effect. > > I've had different problems in the past with Thunderbird every year or > so, on different machines. Wiping the profile and starting over fixed > those. I wonder if that would help in this case too. > > Regards, > Lars > > _______________________________________________ > enigmail-users mailing list > [email protected] > To unsubscribe or make changes to your subscription click here: > https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
signature.asc
Description: PGP/MIME digital signature
_______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
