This is a replacement bug for Netscape bug http://scopus/bugsplat/show_bug.cgi?id=78997 Communicator will not add a certificate to the database with a serial number of "01", if it already has a certificate issued by the same CA with a serial number of "00". ------- Additional Comments From paulmac 03/30/1999 11:40 ------- Moving all Security TFV 5.0 bugs to TFV 5.0 SF1in in preparation for moving them to Bugzilla (per leger) ------- Additional Comments From relyea Jun-09-1999 14:28 ------- This is weird... obviously NSS cert code ------- Additional Comments From relyea Jun-09-1999 14:28 ------- This is weird... obviously NSS cert code ------- Additional Comments From mwelch Jul-01-1999 08:48 ------- This looks like a very narrow edge case, but just in case: is this something we realistically have to deal with in [PSM]?
Set Target Milestone 4.0.
Assignee: lord → wtc
Target Milestone: --- → 4.0
Version: unspecified → 3.0
Is this an SGI specific problem? If so I would like to test if this is still a problem.
No, this is not an SGI specific bug. (The bug reporter had an SGI box.)
OS: IRIX → All
Hardware: SGI → All
Changed the QA contact to Bishakha.
QA Contact: sonja.mirtitsch → bishakhabanerjee
This looks to be working in 173: I just imported an 01 cert where I had an 00 cert before. I am probably out to lunch, but can we get a re-evaluation on this bug?
QA Contact: bishakhabanerjee → jason.m.reid
Assignee: wtc → julien.pierre.boogz
Status: ASSIGNED → NEW
I created certs with serial numbers 0 and 1 from the same CA , the clientCA from our test suite. Here are the commands I used. certutil -d . -S -n Test0 -s "O=bla" -c clientCA -t ,,, -m 0 certutil -d . -S -n Test1 -s "O=bla1" -c clientCA -t ,,, -m 1 It also works fine if they have the same subject and hence the same nickname. I also created a new db, and imported both of their DER successfully, along with the CA cert. Maybe Communicator had a problem showing the 2 certs in that case ? Anyway, the problem does not exist anymore. Marking WORKSFORME.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.