Avatar for Username

Etsi tuesta

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.

Lue lisää

Ketju on suljettu ja arkistoitu. Esitä kysymys, jos tarvitset apua.

Upgraded to 38.2.0. Lost master password selection in Security. Keys and certifcates not available. key3 and cert8 unchanged.

  • 4 vastausta
  • 2 henkilöllä on sama ongelma
  • 3 näyttöä
  • Viimeisin kirjoittaja Wayne Mery

Joaquin
Joaquin
more options

OS X 10.10.

I have used Thunderbird for ten years with a master password and e-mail certificates (XP five years; then OS X five years). Almost all my e-mail messages are encrypted. This is required by my work: I can not send messages unless encrypted.

Using 31.7.0 since release.

Accepted upgrade to 38.2.0. Not asked for master password. >Security>Use a master password unchecked Can't sign message; "... application failed to find the signing certificate..." >Tools>Account Settings>account>Security Digital Signing configuration unchanged: configured as before upgrade. Can't encrypt message; "... application failed to find the encryption certificate..." >Tools>Account Settings>account>Security Encryption configuration unchanged: configured as before upgrade. Can't connect to mail server; "... Could not get password ..." >CertificateManager>Your Certificates and >People display empty. key3.db and cert8.db files appear to be unchanged: Date Modified is date and time of last use of 31.7.0; same size as in profile saved before upgrade. (Have not done binary comparison.)

So: after upgrade, can't send or receive mail. Can't work.

Cordially, Joaquin

OS X 10.10. I have used Thunderbird for ten years with a master password and e-mail certificates (XP five years; then OS X five years). Almost all my e-mail messages are encrypted. This is required by my work: I can not send messages unless encrypted. Using 31.7.0 since release. Accepted upgrade to 38.2.0. Not asked for master password. >Security>Use a master password unchecked Can't sign message; "... application failed to find the signing certificate..." >Tools>Account Settings>account>Security Digital Signing configuration unchanged: configured as before upgrade. Can't encrypt message; "... application failed to find the encryption certificate..." >Tools>Account Settings>account>Security Encryption configuration unchanged: configured as before upgrade. Can't connect to mail server; "... Could not get password ..." >CertificateManager>Your Certificates and >People display empty. key3.db and cert8.db files appear to be unchanged: Date Modified is date and time of last use of 31.7.0; same size as in profile saved before upgrade. (Have not done binary comparison.) So: after upgrade, can't send or receive mail. Can't work. Cordially, Joaquin

Kaikki vastaukset (4)

christ1
christ1
  • Top 25 Contributor
more options

This sounds odd and I don't know what happened either. This is what I'd try: - create a new profile - set up the email account again - import cert and private key to the new profile - see if things are working

If so, you can carry over mail, address book, whatever to the new profile.

Wayne Mery
Wayne Mery
  • Moderator
  • Top 10 Contributor
more options

Joaquin,

Have you seen this problem again since September? Or was it only that one time?

crummyUserInterface
crummyUserInterface
more options

I apologize. I thought I had posted here a message to report what happened when I tried as advised by christ1.

The same thing happened. I have restored the working 31.7.0 and turned off updated.

(Same thing: forgive the run-on text in my first report. I tried to put each step on a new line, but did not put a blank line between each. Here I try to see if hyphens do the trick. - line -another.)

Notice that I was trying to make a jump from v. 31.x to 38.x.

Wayne Mery
Wayne Mery
  • Moderator
  • Top 10 Contributor
more options

Ah!

Let's close this topic and do everything in https://support.mozilla.org/en-US/questions/1100967

Can you file the bug report, if one does not already exist?