The default bug view has changed. See this FAQ.

Deleting certs from ActivCard leaves key material on the token.

RESOLVED FIXED in 3.4

Status

NSS
Libraries
P2
normal
RESOLVED FIXED
16 years ago
15 years ago

People

(Reporter: Stephane Saux, Assigned: Wan-Teh Chang)

Tracking

3.3.1
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
Use the browser to delete dual key certs from an ActivCard token.
Close the browser.
Open the card using the ActivCard utility. The utility shows that there are
still keys on the card.
If you delete certs using the utility everyting goes away.

Note that it doesn't matter whether the certs were generated on the card or
imported from a p12 file.
(Reporter)

Updated

16 years ago
Priority: -- → P2
Target Milestone: --- → 2.2

Comment 1

15 years ago
nsbeta1
Keywords: nsbeta1

Comment 2

15 years ago
WFM with an iButton. Deleting a 1K dual cert from AOL deletes the cert, and it 
does not display in the Admin Utility.
(Reporter)

Comment 3

15 years ago
copy activCard contact.

Comment 4

15 years ago
PSM calls C_DestroyObject for the certificate and the public key, but does not 
calls C_DestroyObject for the private key, thus the private key is not 
destroyed.

Comment 5

15 years ago
Question: Stephan, do you have copies of those certs in your NSS database?

NSS does not destroy the key if it still finds certificates associated with that
key. This can happen one of two ways: 1) the card still reports the existance of
a cert with the same CKA_ID, or 2) we find a cert with the same subject in the
database. I believe the latter is a bug in NSS, which I'll supply a patch for. I
want to make sure the former is not happening as well.

bob

Comment 6

15 years ago
Created attachment 71977 [details] [diff] [review]
Don't lookup the certs elsewhere if we can't find them on the token

This code is used for 2 things: extracting a public key from a private key, and
deciding if we are going to delete the private key from a token. The former 1)
is only used by out utilities 2) has fallbacks if the cert is not found and 3)
is depending on code that was likely to find the wrong cert anyway (the code
deleted in the patch).	For the former we want to succede only if we don't find
any certs in the token we are searching.
(Assignee)

Comment 7

15 years ago
Comment on attachment 71977 [details] [diff] [review]
Don't lookup the certs elsewhere if we can't find them on the token

This patch is fine.  It may be a good idea to
call
    PORT_SetError(SSL_ERROR_NO_CERTIFICATE);
before returning NULL, but I am not sure if that's
the right error code.
(Reporter)

Updated

15 years ago
Keywords: nsbeta1 → nsbeta1-

Comment 8

15 years ago
So Bob has a patch and Wan-Teh likes the patch.
Will you check it in?
The patch is completely within NSS, so it looks like a NSS bug.
Reassining to NSS.
Assignee: ssaux → wtc
Component: Client Library → Libraries
Product: PSM → NSS
QA Contact: junruh → bishakhabanerjee
Target Milestone: 2.2 → ---
Version: 2.1 → unspecified

Updated

15 years ago
Blocks: 157818

Comment 9

15 years ago
This patch has been in NSS since Feb 2002. As such is has already been moved
into NSS 3.5 long ago. I think the bug was left open waiting for a tag move. 
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
(Assignee)

Comment 10

15 years ago
Bob is right.  This bug is fixed in rev. 1.64 of
mozilla/security/nss/lib/pk11wrap/pk11cert.c.
Target Milestone: --- → 3.4
Version: unspecified → 3.3.1
You need to log in before you can comment on or make changes to this bug.