This bug should address upgrade of the crypto and hashing mechanisms implementing PKCS12. It will involve JSS, and/or CS server, and/or client(s).
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1426754
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 @ftweedal: - Issue assigned to ftweedal
commit 633c7c6519c925af7e3700adff29961d72435c7f Author: Fraser Tweedale ftweedal@redhat.com Date: Thu Mar 23 14:34:31 2017 +1100
commit 118f648961e502f55d6997f59f6cf8f355218da5 Author: Fraser Tweedale ftweedal@redhat.com Date: Fri Apr 28 19:45:53 2017 +1000
commit 012718d24aff8c37713f42f2ca69c5bd7aec97df Author: Fraser Tweedale ftweedal@redhat.com Date: Thu Apr 6 13:27:56 2017 +1000
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue set to the milestone: 10.4.3 (was: 10.4) - Issue status updated to: Closed (was: Open)
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/2730
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.