Closed
Bug 478755
Opened 16 years ago
Closed 16 years ago
Add Verisign's Class 3 G5 CA to the 1.8 branch to resolve smtp.mac.com issue
Categories
(Core :: Security: PSM, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: xfox.mozilla, Assigned: KaiE)
References
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; it-IT; rv:1.8.1.19) Gecko/20081204 SeaMonkey/1.1.14
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; it-IT; rv:1.8.1.19) Gecko/20081204 SeaMonkey/1.1.14
Recently Apple renewed the security certificate for its SMTP server smtp.mac.com and now both SeaMonkey 1.1.14 and Thunderbird 2.0.0.19 cannot verify the identity of the SMTP server. If I try to send an e-mail with TLS through smtp.mac.com, now I always get the message: "Unable to verify the identity of smtp.mac.com as a trusted site.". That's because the last server's security certificate is based on the G5 version of the Verisign Class 3 CA that's missing from the products based on the Gecko 1.8 branch. I checked and Firefox 3.0.6, based on the 1.9 branch, has got the G5 version of the certificate.
See this mozillaZine forum's topic for screenshots:
<http://forums.mozillazine.org/viewtopic.php?f=40&t=1081515>.
Reproducible: Always
Steps to Reproduce:
1. Download and install SeaMonkey 1.1.14 or Thunderbird 2.0.0.19.
2. Create a fake account and try to send e-mails with TLS through the smtp.mac.com SMTP server.
Actual Results:
An alert message that states "Unable to verify the identity of smtp.mac.com as a trusted site." is displayed.
Expected Results:
The MUA should successfully verify the identity of the SMTP server.
The smtp.mac.com SMTP server is used by Apple's MobileMe (formerly .Mac) subscribers.
Reporter | ||
Updated•16 years ago
|
Version: unspecified → 1.8 Branch
Comment 1•16 years ago
|
||
Feel free to move somewhere else, not sure where this belongs and if this is wanted.
Assignee: nobody → kaie
Component: Content → Security: PSM
QA Contact: content → psm
Assignee | ||
Comment 2•16 years ago
|
||
1.8 Branch is still using NSS 3.11.9 which contains a set of roots older than 8 months.
See also bug 476157 which proposed to upgrade for similar reasons.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 3•16 years ago
|
||
Fixed with the update to NSS 3.11.10 in bug 476157.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•