Open
Bug 1252069
Opened 9 years ago
Updated 11 months ago
NSS certutil, --rename not working correctly with legacy db ( DBM )
Categories
(NSS :: Tools, defect, P5)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: sdordevi, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150917052249
Steps to reproduce:
1. Create a password file for the security token password
vi pwdfile
Enter some "secretpw"
2. Create the key and certificate databases
certutil -N -d . -f pwdfile
3. Generate the self-signed CA certificate
certutil -S -n "CA certificate" -s "cn=My Org CA cert, dc=example,dc=com" -2 -x -t "CT,," -m 1000 -v 120 -d . -k rsa -n "FIRST_NICK" -f pwdfile
List Certificates from database
# certutil -L -d .
Certificate Nickname Trust Attributes
SSL,S/MIME,JAR/XPI
FIRST_NICK CTu,u,u
4.
# certutil -d . --rename -n FIRST_NICK --new-n SECOND_NICK
# echo $?
0
# certutil -L -d .
Certificate Nickname Trust Attributes
SSL,S/MIME,JAR/XPI
FIRST_NICK CTu,u,u
Actual results:
--rename option finished with exit code 0, but no rename of certificate nickname has occurred.
Expected results:
If "--rename" option has no support for the legacy db ( DBM ) then it should not finish with exit code 0 ( some other exit code ) and should probably give some string back with error message, and if got support for legacy db, should give some string back that rename has occurred and give exit code 0 back.
Updated•2 years ago
|
Severity: normal → S3
Updated•11 months ago
|
Severity: S3 → S4
Priority: -- → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•