Win2000 1.0.0 - Gecko/20020515 Netscape/7.0b1 1.) Install a SmartCard, and exit the browser. 2.) Restart, then Edit>Prefs>Privacy>Certs>Manage Security Devices 3.) Log in to the hardware token. Click OK to close the Device Manager window. 4.) Open the Cert Manager What happens: Crash in nsCharTraits::length 1f0a410a Incident ID - http://climate/reports/SingleIncidentInfo.cfm?dynamicBBID=6321713
Marking works for me on the 5/21 branch and trunk.
Builds: 20020524 Trunk and 20020522 TestBuilds Windows 2k Activcard token and software device token AOL intranet server and Lab212 CA server Old summary: Logging into SCM card then opening Cert Manager crashes browser (Feel free to change the summary once the real cause is known.) Description: Using a fresh profile, install the Activcard module in device manager. In this instance the smartcard used with the reader has a certificate issued from the AOL intranet server. On the software token, - go to https://lab212sun.mcom.com:444/DirUserEnroll1024.html and issue yourself a certificate (at this point you should still be able to view the certs on both tokens via Cert Manager - doesn't matter, but they should all be false as the CA certs have not been imported) - get another cert from the same CA that issued the certs on the smartcard (in this case the AOL intranet server) Reopen the Cert Manager. A crash should occur with the stack trace signature in comment #1. Removing the smartcard allows the user back in to Cert Manager. Deleting either of the two soft token certs enables the certificates on the smartcard to be viewed with other certs in cert manager. I believe the problem lies in the following combination: There are multiple certs from the same issuer on different tokens (AOL on activcard and soft device) and there are one or more certs from other issuers on one or more of the tokens (lab212 on soft device)
This is still happening - http://climate.netscape.com/reports/veryfastsearchEmailNEW.cfm?email=junruh%40ne tscape.com&searchemail=null
WFM. l'm also not seeing the Crash in nsCharTraits::length 1f0a410a in climate.
Verified - the case below was most likely fixed when kai changed the way certs are ordered in the display.