Closed
Bug 546176
Opened 14 years ago
Closed 14 years ago
certutil fails to match nickname with UTF-8 characters
Categories
(NSS :: Tools, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 555261
3.12.7
People
(Reporter: pzb, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20091222 SUSE/3.5.7-1.1.1 Firefox/3.5.7 Build Identifier: When a certificate has a nickname with non-ASCII characters, certutil has trouble finding it. Reproducible: Always Steps to Reproduce: 1. create a db and load the nssckbi module 2. run certutil -d /tmp/certfoo/ -L -n 'Builtin Object Token:TÜBİTAK UEKAE Kök Sertifika Hizmet Sağlayıcısı - Sürüm' Actual Results: certutil: Could not find: Builtin Object Token:TÜBİTAK UEKAE Kök Sertifika Hizmet Sağlayıcısı - Sürüm : Unrecognized Object Identifier. Expected Results: certutil prints the ascii (PEM) version of the certificate
Reporter | ||
Updated•14 years ago
|
Version: unspecified → 3.12.4
Comment 1•14 years ago
|
||
Are you using a shell that's 8-bit clean? Are you using a window that's in UTF8 locale instead of some other locale?
Reporter | ||
Comment 2•14 years ago
|
||
Yes and yes. I'm using bash 3.2 with en_US.UTF-8 locale on Linux. It looks like I'm not the only one having this issue: bug 510367 comment 2 mentions the exact same thing.
Comment 3•14 years ago
|
||
I believe this problem has been independently found and fixed in bug 555261. Presuming that to be the case, I will mark this bug as a duplicate of that one. If this problem persists for you once you are using NSS 3.12.7, please add a comment to this bug or reopen it (if you can).
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Target Milestone: --- → 3.12.7
You need to log in
before you can comment on or make changes to this bug.
Description
•