Closed
Bug 561996
Opened 14 years ago
Closed 10 years ago
UTF8 encoded root names are not displayed correctly in the CRL GUI and the Certificate and CRL GUI
Categories
(Core Graveyard :: Security: UI, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 234856
People
(Reporter: varga.viktor, Unassigned)
Details
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; hu; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; hu; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729) UTF8 encoded root names are not displayed correctly in the CRL GUI and the Certificate and CRL GUI. When a root CA (maybe intemediate too, not tested this case) is displayed, there is some bug in the GUI. Same applies to the CRL GUI too. (Check attached screens.) Reproducible: Always Steps to Reproduce: CRL 1. Download the CRL from the following link: www.netlock.hu/index.cgi?crl=gold 2. Check the CRL data, and you will found display bugs CA 1. Download the CRL from the following link: http://aia1.netlock.hu/index.cgi?ca=cbca 2. Check the CRL data, and you will found display bugs Actual Results: wrong display of the encdoded text Expected Results: correct display of the encdoded text
Reporter | ||
Comment 1•14 years ago
|
||
Reporter | ||
Comment 2•14 years ago
|
||
Reporter | ||
Comment 3•14 years ago
|
||
Updated•13 years ago
|
Version: unspecified → 3.6 Branch
Comment 4•12 years ago
|
||
Confirming this bug: http://harryboeck.dyndns.org/verschiedenes/firefox-certificate-management-charset-bugs.png
Updated•11 years ago
|
Component: Preferences → Security: UI
Product: Firefox → Core
Version: 3.6 Branch → unspecified
Comment 5•10 years ago
|
||
Bug 867465 removed the Revocation Lists feature. The issue seen in Screenshot 1 is valid, but is a dupe of Bug 234856, so marking as such.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•