Crash signing email with certificate from untrusted authority

RESOLVED WORKSFORME

Status

MailNews Core
Security: S/MIME
--
critical
RESOLVED WORKSFORME
15 years ago
9 years ago

People

(Reporter: Ole Dalgaard, Assigned: Stephane Saux)

Tracking

Other Branch
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

In "Certificate Manager" I have a certificate under "Your Certificates" which
under purposes says "<Issuer Not Trusted>".
If I try to sign an email using this certificate, mozilla crash.

If I edit the issuer in "Authorities" and mark "This certificate can identify
web sites" and "This certificate can identify mail users" and "This certificate
can identify software makers", I can sign emails successfully.

Reproducible: Always

Steps to Reproduce:
1. Untrust your certificate issuer (I have a non Builtin. It is called "Software
Security Device)
2. Send a signed email using a certificate from your untrusted issuer.


Actual Results:  
Crash

Expected Results:  
Send a signed email
Reporter: Is this still reproducible with recent mozilla builds?
Summary: Crash when sending email signed with certificate from untrusted authority → Crash signing email with certificate from untrusted authority
(Reporter)

Comment 2

14 years ago
I have tested this again with Mozilla 1.5 and Thunderbird 0.4

Both displays nice error messages explaining what needs to be done to send
signed messages.

Comment 3

14 years ago
Closing WORKSFORME per reporter's latest comment.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME

Updated

13 years ago
Component: Security: S/MIME → Security: S/MIME
Product: PSM → Core

Updated

9 years ago
Component: Security: S/MIME → Security: S/MIME
Product: Core → MailNews Core
QA Contact: bmartin → s.mime
You need to log in before you can comment on or make changes to this bug.