Closed Bug 192727 Opened 21 years ago Closed 21 years ago

Certificates with DERT61String encoded CN cannot be used for signing emails

Categories

(NSS :: Libraries, defect, P3)

x86
Windows 2000
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 192679

People

(Reporter: tkalix, Assigned: wtc)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.3b) Gecko/20030210

We are using our onw CA to issue certificates. All strings are "Printable" type,
unless someone uses a special character (eg. "umlaute", ö). Then we are using
DERT61String to encode the string.


Reproducible: Always

Steps to Reproduce:
1. Get a new certificate and include an "Umlaut" in the CN.
2. Import the certificate with Mozilla.

Actual Results:  
Look in the "Certificate Management". The Value for "Zertificate Name" is empty.
If you look in the details and open "Subject" the CN looks fine (including the
speical character.

If we try to sign an email with this certificate (Special char in CN) Mozilla
Mail will not accept this. It will show the certificate in the Mail-security
settigns, but only part of the details, and once you press [ok] it will jump
back to "no certificate".

Expected Results:  
The "zertificate name" in the cert-manager should be there. And of course it
should work to sign your mails

If you request the Certificate with Netscape 4.7, export it as a .pk12 file and
re-import this into Mozilla, things are working fine. It is just that the
special character itself is not displayed in the right way.
Is the umlauted character a valid T61 character?
Priority: -- → P3
Umlauted characters can be represented in T61 according to the reporter of bug 
192679.  Closing this bug as a duplicate.

*** This bug has been marked as a duplicate of 192679 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.