pki client should have some mechanism to set algorithm/AES encryption .
Like in crmfpopclient we have "-w" option
-w <keywrap algorithm> Algorithm to use for key wrapping - default: "AES KeyWrap/Padding" - "AES/CBC/PKCS5Padding" - "DES3/CBC/Pad"
See additional info documented in the associated bug.
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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1465804 - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical - Issue set to the milestone: 10.5
Metadata Update from @edewata: - Issue set to the milestone: 10.4 (was: 10.5)
Metadata Update from @mharmsen: - Issue assigned to dmoluguw
Per discussions within the PKI Team, moving to 10.5.
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.4)
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Am I correctly assigned to this issue?
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/2890
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.