#2945 Encryption algorithm option for pki pkcs12 CLI
Closed: fixed 6 years ago Opened 6 years ago by edewata.

Currently pki pkcs12 CLI generates a PKCS #12 file with PBE_PKCS5_PBES2. However, Tomcat's built-in HTTP connector so far only works with PBE_SHA1_DES3_CBC. The CLI should provide an option to select which encryption algorithm to use. The default should still be PBE_PKCS5_PBES2.

See also:
https://github.com/dogtagpki/pki/commit/633c7c6519c925af7e3700adff29961d72435c7f

This is needed for ticket #2560.


Metadata Update from @edewata:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

6 years ago

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.6.0 (was: 10.6)
- Issue status updated to: Closed (was: Open)

6 years ago

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/3063

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata