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

Remove support of creating CA on the fly when generating certificates #65590

Merged
merged 3 commits into from
Dec 16, 2020

Conversation

ywangd
Copy link
Member

@ywangd ywangd commented Nov 30, 2020

Generating certificates with the cert sub-command now requires either: 1) a CA to be provided with --ca or --ca-cert/--ca-key; or 2) make them self-signed with the --self-signed option. Generating a CA on the fly is no longer supported. The --keep-ca-key option is removed and the tool throws an error if it is specified.

This is a follow-up PR for #61884, which deprecated the "ca-on-the-fly" usage.

Resolves: #61884

Generating certs now always require a CA to be provided or to be
self-signed.
@ywangd ywangd added >deprecation :Security/Security Security issues without another label v8.0.0 labels Nov 30, 2020
@ywangd ywangd requested a review from tvernum November 30, 2020 11:11
@elasticmachine elasticmachine added the Team:Security Meta label for security team label Nov 30, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security (Team:Security)

Copy link
Contributor

@tvernum tvernum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>breaking :Security/Security Security issues without another label Team:Security Meta label for security team v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Change elasticsearch-certutil default to keep the CA private key
4 participants