parsing more standard OIDs in cert details

RESOLVED WORKSFORME

Status

P1
enhancement
RESOLVED WORKSFORME
17 years ago
2 years ago

People

(Reporter: Bill.Burns, Unassigned)

Tracking

1.0 Branch
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
The client needs to parse more OIDs than it currently does.  In particular it
should parse commonly-used OIDs like
- 2.5.29.15 {key usage}
- 2.5.29.37 and 2.5.29.17 {SubjectAlternativeName}
- 1.3.6.1.5.5.7.1.1 / 1.3.6.1.5.5.7.48.1 {AuthorityInfoAccess and URIName}

for example, certs that don't have an email address in the SubjectDN but *do*
have an RFC822AltName in the cert, it's impossible to see it within PSM.

Comment 1

17 years ago
This is especially important for s/mime (by this bug shouldn't be in the s/mime
component).
Priority: -- → P1
Target Milestone: --- → 2.2

Comment 2

17 years ago
Enhancement.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: RFE: parsing more standard OIDs in cert details → [RFE] parsing more standard OIDs in cert details
Target Milestone: 2.2 → Future
Version: unspecified → 2.3

Comment 3

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.3 → 1.0 Branch

Comment 5

10 years ago
I'm going to claim WFM. Bugs like this are really hard for people to use, each individual case should have a testcase (as an attachment) and pass criteria.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME
Summary: [RFE] parsing more standard OIDs in cert details → parsing more standard OIDs in cert details
(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.