Closed
Bug 106745
Opened 24 years ago
Closed 24 years ago
Need to check S/MIME certificate issued by an untrusted CA
Categories
(MailNews Core :: Security: S/MIME, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
psm2.2
People
(Reporter: alam, Assigned: KaiE)
Details
Build: 2001-10-24-14-OTIS commercial build
The current S/MIME implementation didn't check for error if the S/MIME cert
was issued by an untrusted CA.
Step to reproduce:
1. Obtain a test cert (sectest) from certificate.netscape.com
2. Go to Certificate Manager|Authorities
3. Edit the "Intranet Certificate Authority" CA by uncheking all the trust
settings.
4. Make sure the Root CA "GTE Cyber Trust Root" also has all trust setting
unchecked (default setting)
5. Try to read a sign message with the cert issued by "Intranet Certificate
Authority"
Note that the mail client pop up an alert dialog saying the sign message has a
valid signature.
Comment 1•24 years ago
|
||
ddrinan
Assignee: ssaux → ddrinan
Priority: -- → P1
Target Milestone: --- → 2.2
| Reporter | ||
Updated•24 years ago
|
Component: Client Library → S/MIME
Updated•24 years ago
|
QA Contact: junruh → alam
This is now fine. The text says <invalid signature> now.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 3•24 years ago
|
||
confirmed with build:
/u/kaie/mozilla-win32-nss34-20020201-115010-115209-122961.zip
Clicking on the <invalid signature> also gave me the correct reason why the
signature is invalid (untrusted CA)
But I will wait until I also confirmed with the NSS 3.4 enabled mozilla trunk
build before I marked this as fixed/verified.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 4•24 years ago
|
||
S/MIME bugs are automatically nsbeta1 candidates. (this is a bulk update - there
may be some adjustment of the list).
Keywords: nsbeta1
| Assignee | ||
Comment 6•24 years ago
|
||
Antonio, you said you wanted to wait with verifying. Now that NSS 3.4 is used,
can you please try again?
Comment 8•24 years ago
|
||
Fixed.
Status: NEW → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•