91395 - imported CRL with neither O nor OU shows No name

Status: RESOLVED INCOMPLETE

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

Description

[thomask]

Installed CMS4.2SP2, and Netscape6.1PR1.

Accessed CMS's End-User Retrieval > Import Certificate Revocation List
option, Selected "Import the latest CRL to your browser".

NS6.1 accepted the CRL. But when you do Edit > Preferences > Privacy and 
Security > Validation > Manage CRLs. It shows:

Name                           Last Update          Next Update
  <Empty>                      7/18/2001            7/18/2001

The problem is that the name is empty. Should it show the Issuer name or 
something uniquely identifies the CRL?

FYI, the following is the base64 representation of the CRL:

-----BEGIN CERTIFICATE REVOCATION LIST-----
MIHeMIGJMA0GCSqGSIb3DQEBBAUAMEQxCzAJBgNVBAYTAlVTMREwDwYDVQQKEwhuZXRzY2FwZTEi
MCAGA1UEAxMZQ2VydGlmaWNhdGUgTWFuYWdlciAoU3ViKRcNMDEwNzE4MjMzMjU4WhcNMDEwNzE4
MjM1MjU4WjAUMBICAQwXDTAxMDcxODAyMDIxN1owDQYJKoZIhvcNAQEEBQADQQAIsBqYGZFweo95
8NFt4Dr7PvBj5LUzBfdu/xM3xr8qT8C+N8elVJSrwhiqISu8W4zPSG+UsW4z87HL/gOXL5WR
-----END CERTIFICATE REVOCATION LIST-----

Comment 1

[John Unruh]

This works for me. Can you try a more recent build, like the latest branch 
build? 
ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/2001-07-19-05-0.9.2/

Comment 2

[thomask]

The new build has a new UI. It showed:

O           OU            Last Update          Next Update
200101213ed               7/19/2001            7/19/2001


what if the CA's issuer name does not have O, and OU components,
then those fields will be empty? The name (O, OU) we used here
should be a way to corelate to the CA certificate entry in PSM.
So I suggest we should use something more consistent. For example,
if we display "ABA.ECOM Root CA" in the Authorities entry, the
CRL entry should be named the same way.

Comment 3

[John Unruh]

Can you mark this a dupe of bug 83509 ?

Comment 4

[thomask]

How do they relate?

Comment 5

[John Unruh]

Mass assigning QA to ckritzer.

Comment 6

[Stephane Saux]

Move to future. Won't have time to fix these for 2.1

Comment 7

[Ashley Bischoff (blog at handcoding.com)]

Marking NEW.

Comment 8

[John Unruh]

OS > all

Comment 9

[Kai Engert (:KaiE:)]

So what name should we display, if the CA issuing the cert does neither define a
O nor a OU?

John suggested this should be a duplicate of 83509.

In the hope, a CA would at least define a CN for itself, this would make it less
likely that we do not display any name in the CRL manager.

Comment 10

[John G. Myers]

Mass reassign ssaux bugs to nobody

Comment 11

[Nelson Bolyard (seldom reads bugmail)]

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.

Comment 12

[dave]

There are a number of similar bugs filed, all stemming from the same root cause
for which I've attempted to provide a concise explanation:
https://bugzilla.mozilla.org/show_bug.cgi?id=282945

The solution is simple, but if it is not going to be fixed I would suggest
removing CRL management completely; otherwise it will not work consistently, not
to mention continue to draw new bug reports. 

Comment 13

[Jakob Bohm]

(In reply to comment #12)
> The solution is simple, but if it is not going to be fixed I would suggest
> removing CRL management completely; otherwise it will not work consistently, not
> to mention continue to draw new bug reports. 

DO NOT, UNDER PENALTY OF REVOCATION OF ALL YOUR COMPUTER ACCESS, REMOVE CRL SUPPORT, AND DO NOT EVEN SUGGEST SUCH SABOTAGE AS A SOLUTION TO ANYTHING.

Comment 14

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

The CRL Manager / Revocation Lists feature was removed.