Closed
Bug 121708
Opened 23 years ago
Closed 23 years ago
NSS3.4 Cannot remmber 2 web certs from same server, different ports
Categories
(Core Graveyard :: Security: UI, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
psm2.2
People
(Reporter: junruh, Assigned: ssaux)
References
()
Details
Attachments
(1 file)
807 bytes,
patch
|
wtc
:
review+
|
Details | Diff | Splinter Review |
1.) Visit https://pki.mcom.com:5002
2.) Remember the web site cert.
3.) Visit https://pki.mcom.com/tests.html
4.) Try to remember the web site cert.
What happens: I start an endless loop, unless I click Cancel, twice.
Assignee | ||
Updated•23 years ago
|
Reporter | ||
Comment 1•23 years ago
|
||
*** Bug 121698 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 2•23 years ago
|
||
Can't reproduce with kai 1/28 build.
Marking worksforme
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 4•23 years ago
|
||
Reopening. Reproducible as originally described with the 2/8 Win2000 trunk
build. Removing "NSS3.4" from summary.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
Summary: NSS3.4 Cannot remmber 2 web certs from same server, different ports → Cannot remmber 2 web certs from same server, different ports
Assignee | ||
Comment 5•23 years ago
|
||
updating summary to reflect that this is related to 3.4
Summary: Cannot remmber 2 web certs from same server, different ports → NSS3.4 Cannot remmber 2 web certs from same server, different ports
Assignee | ||
Comment 6•23 years ago
|
||
I reproduced this. I didn't have an endless loop is I didn't try to remember the
second cert.
Comment 7•23 years ago
|
||
Good catch here. The problem is SEC_CERTNicknameConflict is always returning OK,
so PSM does not have a chance to choose a new nickname for the cert.
bob
Comment 8•23 years ago
|
||
Comment 9•23 years ago
|
||
Comment on attachment 69504 [details] [diff] [review]
Implement SEC_CERTNicknameConflict
r=wtc.
Attachment #69504 -
Flags: review+
Assignee | ||
Comment 11•23 years ago
|
||
This appears to be fixed in build id 2002022503
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 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
•