Closed Bug 90510 Opened 24 years ago Closed 23 years ago

certutil -D -n token:certname -h token does not work

Categories

(NSS :: Tools, defect, P2)

Product:
NSS
Component:
Tools
Version:
3.2.1
Platform:
Sun
Solaris
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: sonja.mirtitsch, Assigned: bugz)

Details

tried with and without -h, also without the token before the :, errormeaasge is security library: bad database, doesn't even prompt for password. The same token:cert can be listed with the same commandline just specifieing -L instead of -D (no detail information, just listing)
This will be needed before being able to run the HW accelerator test automatically does the same whether the cert exists or not
Priority: -- → P3
Target Milestone: --- → 3.4
Severity: normal → blocker
I had a partial fix for this in my tree, so I finished it up and checked it in. It works now, however you must use -n "Token Name:Certificate Name".
Thank you Ian. You can go ahead and mark this bug fixed. If you would like someone else to review your patch, please attach it to this bug report.
Assignee: wtc → mcgreer
I read this wrong - the fix I checked in is for 90508, certutil -L. I'll let sonja mark that one fixed if it works correctly. This bug is different and will require more work.
ok, marking FIXED since I checked in, I meant to let sonja verify it.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Ian, did you mean to close this bug or 90508?
If anyone can tell me what I'm on today, I'd like to know. I mean to close 90508, certutil -L not 90510, certutil -D i hate mondays ;)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Mondays? Ian, are you all right? What has big city life done to you?
relyea knows what I'm talking about... Back to the bug, Bob, is there any PK11_ call for deleting a cert off a token? I didn't see one in pk11func.h
Yes, the spirit of Fred lives on..... A bad week is when you've had 5 consecutive Mondays. bob
making this P1, since it should (and will) work in 3.4.
Priority: P3 → P1
can't find server to test this on. Ian is this fixed? Not a P1 blocker from my point of view.
Lowered severity to normal. (The blocker severity means it blocked our effort to run the HW accelerator test automatically. See comment #1.) Ian, does this work now?
Severity: blocker → normal
When push comes to shove, I don't think we should hold up 3.4 release for this fix. Ian, if you already have a patch, or know it already works, or still believe in comment #11 go ahead and change the priority back. bob
Priority: P1 → P2
This is fixed. I tested by trying to delete a builtin using "token name:cert name", and it went through the motions (though it obviously can't actually delete the cert).
Status: REOPENED → RESOLVED
Closed: 24 years ago → 23 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.