Closed Bug 1470077 Opened 2 years ago Closed Last year

SMIME Certificates Not Available

Categories

(Thunderbird :: Security, defect, major)

52 Branch
x86_64
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: as, Unassigned)

References

Details

It's no longer possible to encrypt messages to multiple persons because only the certificate of the first recipient is found. Also it's not possible to import certificates. When exporting a valid cert from an email and try to import it, it doesn't show up - also no error message.

It seems the whole smime support is screwed up since the latest update. Before it worked just fine.
(In reply to as from comment #0)
> It seems the whole smime support is screwed up since the latest update.
> Before it worked just fine.
So which version last worked and which version doesn't?

S/MIME works for me in TB 60 beta 8 on Windows.
(In reply to Jorg K (GMT+2) from comment #1)
> (In reply to as from comment #0)
> > It seems the whole smime support is screwed up since the latest update.
> > Before it worked just fine.
> So which version last worked and which version doesn't?
>

Don't know the last version. But currenty I'm running TB 52.8.0 on Linux

> S/MIME works for me in TB 60 beta 8 on Windows.
I am suffering from the same issue and it is a real pain! :(( it takes forever to send an email, because we only use SMIME for communication and I have to search for an older email of each recipient each time I send an email. grrr :)

I am running 52.9.1 (64-bit) on Kubuntu. Before the last update on Kubuntu it still worked. I thought it was an enigmail issue first because I am using PGP as well and the auto-selection of PGP/SMIME also does not work properly, but as I have disabled it now and SMIME is still not working I am reporting it.

what information would you need to get this fixed or how can I help? This bug is really annoying as I can't send emails properly anymore.
I just installed the beta PPA on Kubuntu from here: https://launchpad.net/~mozillateam/+archive/ubuntu/thunderbird-next

the now installed version 57.0b2 (64-bit) has the same issue as well :(

from the error console I only get the following error messages when clicking on send (SMIME selected):

NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgComposeSecure.beginCryptoEncapsulation]  mimeEncrypt.jsm:172

GenericSendMessage FAILED: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgCompose.SendMsg]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://messenger/content/messengercompose/MsgComposeCommands.js :: GenericSendMessage :: line 3248"  data: no]  MsgComposeCommands.js:3252
i also downloaded thunderbird beta 60 from here: https://download.mozilla.org/?product=thunderbird-60.0b10-SSL&os=linux64&lang=en-US

the certificate manager was empty at initial start and all my certificates were gone and i had to re-import all my private keys and CAs etc. but it seems that TB60b10 stores the certificates correctly and sending emails works. but this beta is completely unusable for me as it crashes very often just by clicking on emails and it is really slow (there is a longer delay when clicking on emails) so i can't use it :(

i went back to the stable version from Kubuntu (52.9.1) and the certificate manager looks empty again now although my private keys/certs are still there (strange?) as I can open all the encrypted emails. and the bug is back, so i can't send emails properly again.
sorry for the update again :) it seems the messages from the error console from above are useless, they also appear on 60b10 just when a certificate for a recipient can't be found
perhaps there are clues in https://mzl.la/2Jl7Q1U
After I removed .thunderbird/****.default/cert8.db everything works fine. Seems like the db was corrupted.
Thanks for letting us know.
Status: UNCONFIRMED → RESOLVED
Closed: Last year
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.