169046 - PSM can't parse subaltname for email in user certs

Status: RESOLVED FIXED

(Core Graveyard :: Security: UI, enhancement, P2)

Description

[bill]

steps to reproduce:
- using Netscpe 7 or Mozilla, get an AOL internal cert
- view the cert in the cert manager and try to find your email address in the
cert (you can't)

This is confusing to some people.  PSM should be able to parse this pretty
typical extension. (I believe it's being encoded in the 2.5.29.17 OID.)

Comment 1

[John Unruh]

I find mine in the cert viewer under "subject".

Comment 2

[bill]

John, I don't think you're using a smartcard-issued certificate.  We no longer
put "E" attributes in people's certificates when they're issued to smartcards,
it's pushed into the SubAltName extension, but PSM doesn't seem to parse them.

If you need help getting a new smartcard, please let me know.

Comment 3

[John Unruh]

Reopening. Can you drop off a blank smartcard the next time you're in bldg. 21?

Comment 4

[Stephane Saux]

John,
You can see the problem by looking at Bill's cert in the cert viewer. Go to the
details section, then look at the extensions. View the details for the
altsubjecname. You can read Bill's email address in the details pane, albeit you
have to translate hex to ascii :-(

We want to improve, but may take a while.

Comment 5

[John Unruh]

Enhancement

Comment 6

[John G. Myers]

Mass reassign ssaux bugs to nobody

Comment 7

[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 9

[:Cykesiopka]

I believe this was fixed by the changes in Bug 259031.