Dogtag currently does not provide any Proof of Possession mechanism for encryption cert requests.
This task will require use of the id-cmc-encryptedPOP and id-cmc-decryptedPOP to complete.
This task will depend on the availability of completed work for underlying JSS ASN.1 code from https://bugzilla.mozilla.org/show_bug.cgi?id=1337092.
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1419742
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: 2
Metadata Update from @mharmsen: - Custom field component adjusted to CMC (was: General) - Custom field origin adjusted to RHCust (was: Community) - Custom field type adjusted to enhancement (was: defect)
commit 58b0563caac110e6950657eb9894c6981f179452 Author: Christina Fu cfu@redhat.com Date: Fri Mar 10 19:50:13 2017 -0800
Bug 1419742: CMC RFE: provide Proof of Possession for encryption cert requests CMC encryptedPOP and decrypedPOP (Phase 1) also disable lraPOPwitness This patch implements the Proof of Possession for encryption only keys. This is a preliminary implementation with limitations. It does not support more than one request. ECC keys are untested. This version only uses default algorithms at some internal places. Not all limitations are listed here.
commit 358064eed09fd43e9fe7b08e43bd03775df880df Author: Christina Fu cfu@redhat.com Date: Sun Mar 26 17:34:51 2017 -0400
Bug #2615 CMC: cleanup code for Encrypted Decrypted POP This patch adds more error checking and debugging
Metadata Update from @cfu: - Issue assigned to cfu - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.4.1 (was: 10.4)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.4.1-1.fc27
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/2735
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.
Login to comment on this ticket.