1. I think version 1.8.x if Enigmail is the last Enigmail that will support GnuPG version 1.x . I ran into this earlier: Enigmail warned me about having a back-level GnuPG . I updated my GnuPG to version 2.0.26 and Enigmail switched to the new GPG of its own accord . I have not encountered any key issues as a result but be aware that GnuPG version 2.1 will be supporting Eliptic Curve (EC) keys -- and I think we will want to move to these as soon as we can . from what I've read they are faster and provide significantly greater resistance
2. did you access the Open PGP Security dialog in your Account Settings and check to see if there is a key specified there ? I have made a habit of setting the key ID myself,-- you just browse to it . 3. when you access the Key Management dialog from the Enigmail main option you should see a lit of all the keys in your system. Any expired key should be greyed out. can you verify that ? 4. as far as the bad key is concerned you might export it -- be sure to export both the public and private keys -- and then delete it from the keyrings. after that you might re-import it and if you do these things the expired key should appear greyed out in the Key Management dialog. 5. I'm using a Debian (LMDE/2) MINT 17.2 system but these are quite similar to the Ubuntu versions. the keyrings are in ~/.gnupg .you should be sure to BACKUP this directory along with ~/.thunderbird when you do your regular backup . 6. the sysops groussed be out for using HTML on this list; I shall try to avoid that. AFAIK in order to sign the message -- as I ought to -- the message should be HTML with PGP_Mime applied and then it can be signed . so until i fugure out what's up with this list i'll just send it unsigned .feel free to reply to mike_ac...@charter.net On 09/02/2015 10:02 AM, Lars Noodén wrote: > On 09/02/2015 04:40 PM, Mike Acker wrote: >> sounds like you have more than one keyring out there.... >> i don't remember where the keyrings are kept in a windows system :( > I never knew where they keyrings are kept in a windows system either, or > for that matter if such a system could even run any of the relevant > applications. > > However, on my systems, the keyring is in ~/.gnupg/ I can't find any > others. It looks like Enigmail is now pointing to gpg2 instead of gpg. > It also looks like it can find all the private keys using the usual > 'gpg2 -K' including the right key. The wrong key that Enigmail is > grabbing is at the head of the list, if that's any clue. > > If I try to decrypt an old message which has been encrypted with the > right key, Enigmail complains with this message: > > "Error - no matching private/secret key found to > decrypt message; click on 'Details' button for more > information" > > If I click on 'key properties' the key information is again the wrong, > expired key and not the key I've been using recent years. > > Regards, > Lars > >> On 09/02/2015 09:35 AM, Lars Noodén wrote: >>> On 09/02/2015 04:19 PM, Mike Acker wrote: >>>> in your Account Settings select OpenPGP dialog and select the key you want >>>> it to use >>> Thanks. It's already set and has been pointing there to the right key >>> for ages and ages. If I set it again, there is only one key there to >>> choose from: the correct key. Even so, Enigmail is able to find and use >>> the wrong key when actually sending and encrypting a message. >>> >>> Now that I try to send this reply, I notice a similar thing for signing. >>> Enigmail says I have the right key but when it actually goes to sign >>> the message, it complains of not found or not valid key until I turn off >>> signing. >>> >>> Regards, >>> Lars >>> >>>> On 09/02/2015 07:22 AM, Lars Noodén wrote: >>>>> With the most recent upgrade of Enigmail on Ubuntu 14.04 LTS, > > $ >>>>> apt-cache policy enigmail > enigmail: > Installed: >>>> 2:1.8.2-0ubuntu0.14.04.1 > ... > > my previous settings are lost and >>>> it is >>>> not using the key it used to > use. Instead of using the active OpenPGP >>>> key it >>>> is using one of my > archived, disabled keys. > > How do I change Enigmail >>>> to >>>> resume using the right key? > > How do I temporarily point it at the >>>> outdated >>>> key so I can at least > decrypt incoming messages which have been >>>> erroneously >>>> encrypted using > the outdated key? > > Regards, > Lars > > > > > > _______________________________________________ > enigmail-users mailing list > enigmail-users@enigmail.net > To unsubscribe or make changes to your subscription click here: > https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net -- /Mike _______________________________________________ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
