Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encryption algorithm option for pki pkcs12 CLI #3063

Closed
pki-bot opened this issue Oct 3, 2020 · 3 comments
Closed

Encryption algorithm option for pki pkcs12 CLI #3063

pki-bot opened this issue Oct 3, 2020 · 3 comments
Milestone

Comments

@pki-bot
Copy link

pki-bot commented Oct 3, 2020

This issue was migrated from Pagure Issue #2945. Originally filed by edewata (@edewata) on 2018-02-20 23:50:24:


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:
633c7c6

This is needed for ticket 2560.

@pki-bot pki-bot added this to the 10.6.0 milestone Oct 3, 2020
@pki-bot pki-bot closed this as completed Oct 3, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from edewata (@edewata) at 2018-02-28 18:29:23

Fixed in master:

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from edewata (@edewata) at 2018-02-28 18:29:25

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

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from edewata (@edewata) at 2018-02-28 18:29:50

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant