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.
Additional comment
Support requires pretty prints, encoding and decoding procedures, administrative interface support, and enrollment profile support.
This issue was migrated from Pagure Issue #659. Originally filed by awnuk (@awnuk) on 2013-06-14 00:18:08:
Bug 509481 - Original description
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.
Additional comment
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