Closed Bug 62116 Opened 24 years ago Closed 19 years ago

PSM has problem in importing a certificate has UniversalString type of data

Categories

(Core Graveyard :: Security: UI, defect, P3)

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Platform:
x86
All
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: javi, Unassigned)

Details

Procedure to reproduce
-Communicator 4.7 w/ PSM or Netscape6
-WinNT4.0 Korean Edition

1. With EE-Manual enrollment page issue a certificate request. - For fullname
and organization, specify korean character
2. With Agent page accept the request and issue a certificate.
3. With EE-Retrieval/list-certificate page, open the certificate and click
"Import" Button.

Even if I click the button several times, certificate is not imported. But, it
works fine with english based certificate.
Target Milestone: --- → 2.0
Wan-Teh,
Does NSS support ucs-2 strings in certs?
NSS has code that is supposed to decode BMPString, which is either UCS-2
or UTF-16.
target 2.1
Target Milestone: 2.0 → 2.1
Keywords: nsenterprise
remove nsenterprise
Keywords: nsenterprise
I18N->P3
Moving all P3 and P4 bugs targetted to 2.1 to future.
Target Milestone: 2.1 → Future
Mass assigning QA to ckritzer.
QA Contact: junruh → ckritzer
QA Contact: ckritzer → junruh
Component: Daemon → Client Library
QA Contact: junruh → bmartin
Mass reassign Javi's old PSM bugs to nobody
Assignee: javi → nobody
QA Contact: bmartin → nobody
Target Milestone: Future → ---
Product: PSM → Core
very old bug, no testcase cert available, nobody ran into the issue during the last 5 years, wontfix
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Version: psm1.4 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.