Add API and application support for RFC 4043 (X.509 Permanent Identifier)

RESOLVED WONTFIX

Status

()

Core
Security: PSM
--
enhancement
RESOLVED WONTFIX
12 years ago
2 years ago

People

(Reporter: Ken Johanson, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

ftp://ftp.rfc-editor.org/in-notes/rfc4043.txt

Descibes a standard for describing relationships (i.e. same-subject, i.e. LUID, or UUID) between certficates and/or the issuing authorites, so that email applications can reasonably assert that emails signed by a same person but with different certs (due to expiry, vendor change, etc) are one and the same, or so that an Address book can auto detect that a changed (signed) email address is actually same person, or so that a WWW browser can assert that two different websites (each possibly having a different cert and/or issuer) are representative of the same owning company (e.g. https://www.mosilla.org and https://bugzilla.mozilla.org).


Reproducible: Always

Steps to Reproduce:
1. None



Expected Results:  
In the case of RFC 4043, Moz apps should be able to identify when two or more x509 certs are referring to the same subject.

Upcoming 3rd products (Apple and Microsoft, and X.509 Certificate Authority) and standards (various single-sign-on systems) are eveidently going to support this standard. Mozilla should also.

Keywords: SSO, SASL, SAML, UUID, GUID, OID, PermanentIdentifier, PermanentId, NSAPI.

This feature also has a slight relation to RFC 3709 -- in that both appear to be imminent in other products.
(Reporter)

Updated

12 years ago
Summary: Add API and application support for RFC 4043 → Add API and application support for RFC 4043 (X.509 Permanent Identifier)

Updated

12 years ago
Assignee: kengert → nobody
QA Contact: psm
Resolving unconfirmed bugs older than a year with no activity as INCOMPLETE.  Please reopen or file a new bug if you can still reproduce the bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE

Comment 2

8 years ago
This bug was auto-closed due to inactivity.

But it sounds like it might be a valid enhancement request, let's keep it open, so it can be found.

However, unless someone is willing to contribute patches, this is unlikely to get implemented in the near future.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INCOMPLETE → ---
We have no plans to implement this at the moment.
Status: REOPENED → RESOLVED
Last Resolved: 8 years ago2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.