RFC 4262 defines a new certificate extension which is merely an sMIMECapabilities SEQUENCE, just like the one put into a signed S/MIME email. Microsoft's Certificate Server product puts these extensions into S/MIME encryption certs that it issues. DogTag should fully support them.
This certificate extension has an identifying OID of sMIMECapabilities (1 2 840 113549 1 9 15) and the OCTET STRING encapsulates a data structure that is identical to the data structure of the SMIMECapabilities attribute defined in RFC 3851.
Support requires pretty prints, encoding and decoding procedures, administrative interface support, and enrollment profile support.
http://tools.ietf.org/html/rfc4262
http://tools.ietf.org/html/rfc3851
http://tools.ietf.org/html/rfc5751
https://bugzilla.redhat.com/show_bug.cgi?id=509481
https://bugzilla.redhat.com/show_bug.cgi?id=652482
Metadata Update from @awnuk: - Issue set to the milestone: UNTRIAGED
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/1229
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
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)
Login to comment on this ticket.