Re: [Enigmail] New enigmail archives/signs with outdated, disabled key
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
Re: [Enigmail] pinentry crashes, only on Enigmail?
Is there a gpg-agent running on your system before you start another gpg-agent using the standard socket ? Patrick - Original Message - From: Nathan Ringo Sent: 02.09.2015 - 21:54 To: enigmail-users@enigmail.net Subject: Re: [Enigmail] pinentry crashes, only on Enigmail? > The plot thickens. When I try to encrypt something with a key whose > password is shorter than the crash-length, I get a popup saying: > > Send operation aborted. > > Error - encryption command failed > > If I click Cancel instead of entering a password, Enigmail prepends > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > but has no appended cryptoblock. GNOME then crashed moments later, but > that might've been a coincidence? I think it had something to do with > Enigmail/pinentry/gpg-agent though. As always, having the debugging > gpg-agent open completely removes all traces of a problem. > > On 09/01/2015 01:48 AM, Nathan Ringo wrote: >> When I'm typing my password into pinentry, it crashes partway >> through. Enigmail then says "no matching private/secret key found >> to decrypt message". When I run >> >> gpg-agent --debug-level expert --use-standard-socket --daemon >> /bin/sh >> >> as proscribed in the support page, the problem ceases to exist. I >> can use command-line gpg with graphical pinentry just fine. The >> combination of these two factors makes me suspect that the issue's >> in how Enigmail connects to gpg-agent, but I might be wrong. >> > > ___ > 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 signature.asc Description: PGP/MIME digital signature ___ 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
Re: [Enigmail] New enigmail tries to decrypt with outdated, disabled key
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" Sent: 02.09.2015 - 21:30 To: Enigmail user discussion list 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 0x 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 > enigmail-users@enigmail.net > 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] pinentry crashes, only on Enigmail?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The plot thickens. When I try to encrypt something with a key whose password is shorter than the crash-length, I get a popup saying: Send operation aborted. Error - encryption command failed If I click Cancel instead of entering a password, Enigmail prepends -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 but has no appended cryptoblock. GNOME then crashed moments later, but that might've been a coincidence? I think it had something to do with Enigmail/pinentry/gpg-agent though. As always, having the debugging gpg-agent open completely removes all traces of a problem. On 09/01/2015 01:48 AM, Nathan Ringo wrote: > When I'm typing my password into pinentry, it crashes partway > through. Enigmail then says "no matching private/secret key found > to decrypt message". When I run > > gpg-agent --debug-level expert --use-standard-socket --daemon > /bin/sh > > as proscribed in the support page, the problem ceases to exist. I > can use command-line gpg with graphical pinentry just fine. The > combination of these two factors makes me suspect that the issue's > in how Enigmail connects to gpg-agent, but I might be wrong. > ___ 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
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 0x 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 enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] New enigmail archives/signs with outdated, disabled key
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. > 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. > If I try to sign an outgoing message, I get this: > > Key 0x 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? [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)? Ludwig signature.asc Description: OpenPGP digital signature ___ 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
Re: [Enigmail] New enigmail archives/signs with outdated, disabled key
On 09/02/2015 09:09 PM, Ludwig Hügelschäfer wrote: > On 02.09.15 19:56, Lars Noodén wrote: >> >> I can encrypt and send to another machine and decrypt there using the >> same ~/.gnupg contents. >> >> I also went through the Enigmail setup wizard again to reset the key and >> it still shows the right key but when I try to decrypt, Enigmail still >> looks for the wrong key. > > The key to decrypt is always selected automatically. The key-Id of the > receiver(s) is/are embedded in the message. You cannot decrypt a given > message with another (newer) key. What makes you think it Enigmail looks > for the wrong key? Please give us the exact error message. The error message between the message body and the headers is : Enigmail Error - decryption failed; click on 'Details' button for more information. 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. If I try to sign an outgoing message, I get this: Key 0x 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 have any additional settings like "encrypt-to" in your gpg.conf file? > > Ludwig 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 comment GPGTools - http://gpgtools.org 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
Re: [Enigmail] New enigmail archives/signs with outdated, disabled key
On 02.09.15 19:56, Lars Noodén wrote: > > I can encrypt and send to another machine and decrypt there using the > same ~/.gnupg contents. > > I also went through the Enigmail setup wizard again to reset the key and > it still shows the right key but when I try to decrypt, Enigmail still > looks for the wrong key. The key to decrypt is always selected automatically. The key-Id of the receiver(s) is/are embedded in the message. You cannot decrypt a given message with another (newer) key. What makes you think it Enigmail looks for the wrong key? Please give us the exact error message. Do you have any additional settings like "encrypt-to" in your gpg.conf file? Ludwig signature.asc Description: OpenPGP digital signature ___ 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
Re: [Enigmail] New enigmail archives/signs with outdated, disabled key
On 09/02/2015 07:47 PM, Lars Noodén wrote: > On 09/02/2015 07:37 PM, Ludwig Hügelschäfer wrote: >> On 02.09.15 15:35, Lars Noodén wrote: >> >>> 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. >> >> Is your key not expired and has ownertrust set to "Ultimate"? >> >> Ludwig > > Yes to both. As far as I know, nothing has changed with the key since > when it was working. I did upgrade Engimail from 1.7.2-0ubuntu0.14.04.1 > to 1.8.2-0ubuntu0.14.04.1 on the 27th and restarted Thunderbird today. > It was after this restart that the encryption stopped working. A few > minutes prior to that, it was ok. > > Regards, > Lars I can encrypt and send to another machine and decrypt there using the same ~/.gnupg contents. I also went through the Enigmail setup wizard again to reset the key and it still shows the right key but when I try to decrypt, Enigmail still looks for the wrong 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
Re: [Enigmail] New enigmail archives/signs with outdated, disabled key
On 09/02/2015 07:37 PM, Ludwig Hügelschäfer wrote: > On 02.09.15 15:35, Lars Noodén wrote: > >> 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. > > Is your key not expired and has ownertrust set to "Ultimate"? > > Ludwig Yes to both. As far as I know, nothing has changed with the key since when it was working. I did upgrade Engimail from 1.7.2-0ubuntu0.14.04.1 to 1.8.2-0ubuntu0.14.04.1 on the 27th and restarted Thunderbird today. It was after this restart that the encryption stopped working. A few minutes prior to that, it was ok. 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
Re: [Enigmail] New enigmail archives/signs with outdated, disabled key
On 02.09.15 15:35, Lars Noodén wrote: > 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. Is your key not expired and has ownertrust set to "Ultimate"? Ludwig signature.asc Description: OpenPGP digital signature ___ 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
Re: [Enigmail] New enigmail archives/signs with outdated, disabled key
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
Re: [Enigmail] New enigmail archives/signs with outdated, disabled key
On 02.09.2015 15:40, 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 :( He wrote that he is on Ubuntu. signature.asc Description: OpenPGP digital signature ___ 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
Re: [Enigmail] New enigmail archives/signs with outdated, disabled key
sounds like you have more than one keyring out there i don't remember where the keyrings are kept in a windows system :( 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
Re: [Enigmail] New enigmail archives/signs with outdated, disabled key
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
Re: [Enigmail] New enigmail archives/signs with outdated, disabled key
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 in your Account Settings select OpenPGP dialog and select the key you want it to use 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 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJV5vdpAAoJEMxYQmPg90u5DuEH/i72DEaGdKgArpNdi4+oT5Yr goTDkH2i3u95K7cQodkwlPbCKY0JjFl2cnj/VPWVv7YOGeUbVN7B883FaRGRr5u5 hKOTwb5C8SlpHKp9C5nDPDN2qlqIY2MGUkFA9cehMw30EfgDJnNtGl8d2Co1FxWp 5y6TIQoE16DjQyoPU42pEEU7rXsrX5y5Lz/JyRWW3R4Lby3e7/00BiDoEXw0GB2W IZHGwag4L0jyvZGx4QuWZ9xiMy6qsBK1rCTD3YeODzzR51n3IHk/Y6EZ/bGZz6aS lmlnH4w363BjI+GzfYg9EoCl+VrT5gSno3pMGPCa7O3odEJXrNn5jap0SttGSQc= =jNmE -END PGP SIGNATURE- ___ 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
[Enigmail] New enigmail archives/signs with outdated, disabled key
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
