Closed
Bug 524406
Opened 15 years ago
Closed 15 years ago
SSL/IMAP cert chain regression?
Categories
(Thunderbird :: Security, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: bob.lord, Unassigned)
Details
Attachments
(2 files)
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.5pre) Gecko/20091025 Shredder/3.0pre
My mail server uses SSL/IMAP for client connections. Starting tonight, I started getting prompted to trust my mail server's certificate. The dialog in question is the one that reads:
You are about to override how Shredder identifies this site.
Legitimate banks, stores...
I'll attach a screenshot.
So far as I can tell, the mail server certificate is fine, and it chains to the corporate root. I had previously marked this root as trusted and have not had any issues until tonight.
I manually trusted the cert (but did not allow it to "Permanently store this exception"), and was able to connect to the server and get my mail. So that part of the connection still works.
It is quite possible that there is a server configuration error, but it feels more like a client regression.
Does anyone else use SSL/IMAP on a regular basis?
Comment 1•15 years ago
|
||
(In reply to comment #0)
> Does anyone else use SSL/IMAP on a regular basis?
Daily as gmail uses that by default. Haven't notices your issue.
caillon are you seeing the issue too ?
Updated•15 years ago
|
Component: Mail Window Front End → Security
QA Contact: front-end → thunderbird
Comment 2•15 years ago
|
||
My only thought is something in bug 522633 affected this.
Comment 3•15 years ago
|
||
Yes, I see this as well (with Fedora TB), but I am afraid there is something phoney about changes of certificates on the server.
(In reply to comment #2)
> My only thought is something in bug 522633 affected this.
That bug was about SMTP, whereas attachment 408314 [details] affects IMAP.
Unless your server offers GSSAPI (only), you shouldn't see any change.
I think this turned out to be a server config issue. Feel free to close.
You need to log in
before you can comment on or make changes to this bug.
Description
•