#88 Code submission by Josh Roys: [PATCH] Add support for RFC4043 permanent identifiers
Closed: migrated 3 years ago by dmoluguw. Opened 12 years ago by vakwetu.

Date: Fri, 16 Dec 2011 14:35:41 -0500

Hello,

Attached is a patch to implement (half of) RFC4043 Permanent
Identifiers. The cases where the identifierValue is not supplied are
not supported. (This was tested on pki 1.3.x and sometime soon I will
test it on 9.0.x also.)

I'm not sure if the code reformatting is done yet, so I'll rebase this
patch later if need be. Also, either a V2 of this patch or a follow-up
will add pretty-printing.

Josh


Thanks for submitting the code. A couple questions: 1. in the Description it says that this "is a patch to implement (half of) RFC4043 Permanent Identifiers." Which half is that? (what's implemented and what's not?) 2. Do you know of any publicly available client that supports this RFC? Thanks! - Christina

Hello Christina,

You're welcome. According to the RFC, there are four combinations of two OPTIONAL values (search for "The various combinations are detailed below:" in the RFC). Cases three and four where the identifierValue is absent are not supported with the current code. However, re-reading the text it is possible I misinterpreted it and the language is geared towards the client w.r.t. a missing identifierValue requiring the use of a serialNumber... For comment 2, I was unable to find much on existing implementations, and I even found a few incorrectly implemented (I don't actually recall finding a "good" one). Due in part to this and changing requirements on our end, it looks like this extension won't be necessary for us.

Josh

Metadata Update from @vakwetu:
- Issue assigned to vakwetu
- Issue set to the milestone: UNTRIAGED

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/660

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata