Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

TB cannot find my PgP keys

  • 2 odgovori
  • 0 ima ovaj problem
  • 1 view
  • Posljednji odgovor poslao alvaro15

more options

I have TB, Windows 10 64x and I only use Firefox as browser. I keep all up to date.

I use several email accounts from different domains and mail service providers, and I digitally signed for two of them with PgP. Up to two months ago, I was doing so with no problem -with Enigmail originally, and then with the integrated system in TB.

About two months ago, I installed one official -Goverment- certificate in Firefox (not in TB) but -coincidence or not, but I wanted to mention it just in case.

A few days after one TB update, I was unable to sign any mail digitally, and since then I get the following message The configured key XXXXXXXXXXXXXXXXXXXXXXXX cannot be found on your keyring.

I erased previous keys and created/generated new ones, and I tagged them as personal keys, but it still does not work. I erased all of them again, set one of the email addresses as preferred account in TB, generated the new keys, and I still get the same problem.

Furthermore. When I generate a new key, if I try to refresh it in TB keymanager menu, it responds "We could not find any usable key with matching criteria", in spite that the key that has just been generated, still appears in the key manager.

Thus, I cannot encrypt or digitally sign any mails.

The Console shows the following:

GenericSendMessage FAILED: [Exception... "compose-send-message prevented" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "JS frame :: chrome://messenger/content/messengercompose/MsgComposeCommands.js :: CompleteGenericSendMessage :: line 5943" data: no] MsgComposeCommands.js:5995 [Exception... "compose-send-message prevented" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "JS frame :: chrome://messenger/content/messengercompose/MsgComposeCommands.js :: CompleteGenericSendMessage :: line 5943" data: no]

Any input will be more than welcome

Al

I have TB, Windows 10 64x and I only use Firefox as browser. I keep all up to date. I use several email accounts from different domains and mail service providers, and I digitally signed for two of them with PgP. Up to two months ago, I was doing so with no problem -with Enigmail originally, and then with the integrated system in TB. About two months ago, I installed one official -Goverment- certificate in Firefox (not in TB) but -coincidence or not, but I wanted to mention it just in case. A few days after one TB update, I was unable to sign any mail digitally, and since then I get the following message '''The configured key XXXXXXXXXXXXXXXXXXXXXXXX cannot be found on your keyring.''' I erased previous keys and created/generated new ones, and I tagged them as personal keys, but it still does not work. I erased all of them again, set one of the email addresses as preferred account in TB, generated the new keys, and I still get the same problem. Furthermore. When I generate a new key, if I try to refresh it in TB keymanager menu, it responds "We could not find any usable key with matching criteria", in spite that the key that has just been generated, still appears in the key manager. Thus, I cannot encrypt or digitally sign any mails. The Console shows the following: GenericSendMessage FAILED: [Exception... "compose-send-message prevented" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "JS frame :: chrome://messenger/content/messengercompose/MsgComposeCommands.js :: CompleteGenericSendMessage :: line 5943" data: no] MsgComposeCommands.js:5995 [Exception... "compose-send-message prevented" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "JS frame :: chrome://messenger/content/messengercompose/MsgComposeCommands.js :: CompleteGenericSendMessage :: line 5943" data: no] Any input will be more than welcome Al

Izabrano rješenje

About two months ago, I installed one official -Goverment- certificate in Firefox (not in TB) but -coincidence or not, but I wanted to mention it just in case.

Firefox is a separate application, thus irrelevant to your problem.

I erased previous keys and created/generated new ones, and I tagged them as personal keys, but it still does not work.

Did you also set up the new key for your account(s)? At the top right of the Thunderbird window, click the menu button ≡ > Account Settings > End-To-End Encryption Make sure the correct key for the account is selected there. Only accepted personal keys with a matching email address will be offered.

Just in case ... https://support.mozilla.org/en-US/kb/openpgp-thunderbird-howto-and-faq

Pročitajte ovaj odgovor sa objašnjenjem 👍 1

All Replies (2)

more options

Odabrano rješenje

About two months ago, I installed one official -Goverment- certificate in Firefox (not in TB) but -coincidence or not, but I wanted to mention it just in case.

Firefox is a separate application, thus irrelevant to your problem.

I erased previous keys and created/generated new ones, and I tagged them as personal keys, but it still does not work.

Did you also set up the new key for your account(s)? At the top right of the Thunderbird window, click the menu button ≡ > Account Settings > End-To-End Encryption Make sure the correct key for the account is selected there. Only accepted personal keys with a matching email address will be offered.

Just in case ... https://support.mozilla.org/en-US/kb/openpgp-thunderbird-howto-and-faq

more options

Thanks for the prompt answer and solution.

The question is that I was unable to neither import the old keys nor to make works the last set of keys I made yesterday.

I even exported the keys created yesterday (using the KeyManager export feature) and got an error message when importing them.

So, I erased all keys, and created new ones -THIS TIME DIRECTLY FROM THE ≡ > Account Settings > End-To-End Encryption - and this time it worked. I don't know why it did not work from PgP Key Manager (neither accessing directly or accessing through the shortcut of the End-To-End Encryption.

Anyhow, good news. It all works now.

Thanks again