Closed
Bug 119578
Opened 23 years ago
Closed 17 years ago
parsing more standard OIDs in cert details
Categories
(Core Graveyard :: Security: UI, enhancement, P1)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: Bill.Burns, Unassigned)
Details
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•23 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•23 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 4•21 years ago
|
||
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•18 years ago
|
QA Contact: junruh → ui
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
Closed: 17 years ago
Resolution: --- → WORKSFORME
Summary: [RFE] parsing more standard OIDs in cert details → parsing more standard OIDs in cert details
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•