Closed
Bug 437080
Opened 16 years ago
Closed 2 years ago
Firefox crashes when Leopard 10.5.3 PKCS#11 module is loaded into secmod.db.
Categories
(NSS :: Libraries, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: tmiller, Unassigned)
Details
Attachments
(1 obsolete file)
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_3; en-us) AppleWebKit/525.18 (KHTML, like Gecko) Version/3.1.1 Safari/525.20 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9) Gecko/2008051202 Firefox/3.0 Loading the PKCS#11 module provided by Apple as part of PC/SC support crashes Firefox with a EXC_BAD_ACCESS / KERN_INVALID_ADDRESS error. Reproducible: Always Steps to Reproduce: 1. Attach supported CCID reader (SCM SCR3310 used locally) 2. Insert system supported smartcard (DoD CAC used locally) 3. Launch FF. 4. Open Preferences, go to Advanced | Encryption | Security Devices. 5. Select module file: /usr/libexec/SmartCardServices/pkcs11/pkcs11.bundle/Contents/MacOS/pkcs11 6. Click OK. Actual Results: FF crashes. Expected Results: Module is loaded and smartcard is available to NSS. Crash Reported example: http://crash-stats.mozilla.com/report/index/02e37114-318e-11dd-be9c-001cc4e2bf68?date=2008-06-03-16
Updated•16 years ago
|
Assignee: nobody → nobody
Component: Security → Libraries
Product: Firefox → NSS
QA Contact: firefox → libraries
Version: unspecified → 3.12
Comment 1•16 years ago
|
||
The stack shown in the trace in the crash you cited clearly shows that its crashing in the PKCS#11 module's C_Initialize function. You need to report this to the Mac people responsible for that PKCS#11 module.
Reporter | ||
Comment 2•16 years ago
|
||
Did that last year; Apple bug # is #5179294 if anyone is interested, updated today with a reference to this issue. I'm looking to shake something loose over there as well.
Comment hidden (spam) |
Updated•8 years ago
|
Attachment #8757579 -
Attachment is obsolete: true
Attachment #8757579 -
Attachment is patch: false
Flags: needinfo?(qlwlgfgioq)
Comment 4•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: critical → --
Updated•2 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•