Closed
Bug 198470
Opened 23 years ago
Closed 23 years ago
Cached certs not updated after token reset.
Categories
(NSS :: Libraries, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
3.8
People
(Reporter: rrelyea, Assigned: rrelyea)
Details
Attachments
(1 file)
|
553 bytes,
patch
|
bugz
:
review+
wtc
:
superreview+
|
Details | Diff | Splinter Review |
When we reset the token (which clears the keys), the certificates stored in
those tokens are not getting updated, so they still look like valid user certs
to the application, even though the no longer have any associated private keys.
| Assignee | ||
Comment 1•23 years ago
|
||
Comment 3•23 years ago
|
||
Adding Javier to the bug
| Assignee | ||
Updated•23 years ago
|
Attachment #117904 -
Flags: superreview?(wtc)
Attachment #117904 -
Flags: review?(ian.mcgreer)
Updated•23 years ago
|
Attachment #117904 -
Flags: review?(ian.mcgreer) → review+
Comment 4•23 years ago
|
||
Comment on attachment 117904 [details] [diff] [review]
Update cached certs after token reset.
r=wtc.
Attachment #117904 -
Flags: superreview?(wtc) → superreview+
| Assignee | ||
Comment 5•23 years ago
|
||
Checked into NSS 3.8
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•