user-friendly names should handle case where there's no CN field

RESOLVED WONTFIX

Status

P2
enhancement
RESOLVED WONTFIX
18 years ago
2 years ago

People

(Reporter: thomask, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
I have created a certificate with the following subject name

UID=thomask,dc=iplanet,dc=com.

In the Manage certificate dialog of NS61PR1, it shows:

's netscape ID

Wouldnt it be nicer to display just thomask or even
UID=thomask,dc=iplanet,dc=com.

The user-friendly name building logic may just print the
subject if a user-friendly name cannot be built.

Comment 1

18 years ago
->future
P2
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Target Milestone: --- → Future

Comment 2

18 years ago
Mass assigning QA to ckritzer.
QA Contact: junruh → ckritzer

Updated

17 years ago
QA Contact: ckritzer → junruh

Comment 3

16 years ago
May I suggest wontfix? Reporter, you may have the world's only cert without a 
CN.
(Reporter)

Comment 4

16 years ago
The subject name can have anything there according to the X509
standard. CN is not a mandatory field. The subject name is
determined by the certificate authority or the issuer. So really,
it can be anything as long as it is in the format of name=value,
name=value,...

I will not be suprised to see PKI deployment where CN is not
present in user certificates.

If you look at Microsoft's Certificate management, they handle
it as follows:

Subject Name                           Pretty Print Name
----------------------------------------------------------
UID=thomask                            thomask
E=thomask@netscape.com                 thomask@netscape.com
CN=Thomas Kwan                         Thomas Kwan
UID=thomask,CN = Thomas Kwan,...       Thomas Kwan


Comment 5

15 years ago
Mass reassign ssaux bugs to nobody
Assignee: ssaux → nobody
Mass change "Future" target milestone to "--" on bugs that now are assigned to
nobody.  Those targets reflected the prioritization of past PSM management.
Many of these should be marked invalid or wontfix, I think.
Target Milestone: Future → ---

Updated

14 years ago
Component: Security: UI → Security: UI
Product: PSM → Core
QA Contact: junruh → ui

Updated

10 years ago
Version: psm2.0 → 1.0 Branch

Updated

10 years ago
Summary: NS61PR1 inappropriately handles user-friendly names → user-friendly names should handle case where there's no CN field
Version: 1.0 Branch → Trunk
From what I can tell, the browser will default to "Imported Certificate" if it can't figure out a reasonable name. This is probably the best we can do without putting significant effort into attempting to come up with something based on properties that may or may not be present and may or may not be relevant or even human-readable.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
(Assignee)

Updated

2 years ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.