Closed
Bug 115699
Opened 24 years ago
Closed 24 years ago
NSS3.4 build. Sending signed email crashes browser.
Categories
(Core Graveyard :: Security: UI, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
psm2.2
People
(Reporter: junruh, Assigned: KaiE)
References
Details
1.) Use a trunk 6.2 build to select signing and encrypting certs, and select to
sign messages, encrypt if possible. Close the app.
2.) Start the mozilla NSS4.3 build, using the same profile you just used to set
the email preferences in 6.2
3.) Send an email.
What happens: Crash.
Comment 1•24 years ago
|
||
cc kai.
NSS3.4
Priority: -- → P1
Summary: NSS4.3 build. Sending signed email crashes browser. → NSS3.4 build. Sending signed email crashes browser.
Target Milestone: --- → 2.2
Comment 2•24 years ago
|
||
cc relyea
| Assignee | ||
Comment 3•24 years ago
|
||
The crash is caused by an assertion in certhigh.c - CERT_FindUserCertsByUsage,
called with "oneCertPerName" enabled. The section "remove any extra certs" is
reached. The outer loop iterates over certList, assuming that for each
node->cert->nickname, there is an entry in the nnptr array which a matching
nickname.
Entries in nnptr have a qualified nickname, i.e. they are "tokenname:nickname".
But node->cert->nickname is just a nickname without token name.
No match is found, and the assertion PORT_Assert(0) is triggered.
Comment 5•24 years ago
|
||
This crash should be fixed on the tip of NSS 3.4.
| Assignee | ||
Comment 6•24 years ago
|
||
I am now able to send signed messages.
Marking fixed.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•