I am NSS3.2 pk12util on Solaris 8. I did the follwing: 1. ./certutil -N -d certdir 2. certutil -S -n cert_root -s 'C=US,O=B,CN=C' -x -t "TCu,Cu,Tuw" -d certdir cert/key generate are fine. Then I did. 3. ./pk12util -d certdir -o test.pk12 -n cert_root I got: pk12util: add cert and key failed.
Moving to NSS
Component: Security: Crypto → Tools
Product: Browser → NSS
Version: other → 3.0
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA > ckritzer
QA Contact: junruh → ckritzer
Assigned the bug to Ian.
Assignee: ddrinan → ian.mcgreer
Priority: -- → P2
Target Milestone: --- → 3.4
This works in our tinderbox solaris machines, so I'm not sure how to reproduce it. You might not want to set the "w" flag in your trust string.
Set target milestone to NSS 3.5.
Target Milestone: 3.4 → 3.5
On Solaris 8, with both NSS 3.2 and the NSS tip (3.6 pre-release), this works for me. I get pk12util: PKCS12 EXPORT SUCCESSFUL
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.