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.

Sign up for GitHub

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

Jump to bottom

certutil http command kibana PKCS #12 #50932

Open
kobelb opened this issue Jan 13, 2020 · 2 comments
Open

certutil http command kibana PKCS #12 #50932

kobelb opened this issue Jan 13, 2020 · 2 comments
Labels
>enhancement :Security/TLS SSL/TLS, Certificates Team:Security Meta label for security team

Comments

@kobelb
Copy link
Contributor

kobelb commented Jan 13, 2020 •
edited
Loading

Now that Kibana supports PKCS #12, the certutil's http command can be modified to output PKCS #12 certs for Kibana. Continuing to use PEM is fine as well, but it PKCS #12 would keep Kibana consistent with Elasticsearch.
@kobelb kobelb added >enhancement :Security/TLS SSL/TLS, Certificates labels Jan 13, 2020
@elasticmachine
Copy link
Collaborator

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

@kobelb kobelb changed the title certutil http command kibana PCKS #12 certutil http command kibana PKCS #12 Jan 13, 2020
@rjernst rjernst added the Team:Security Meta label for security team label May 4, 2020
@ghost
Copy link

ghost commented Mar 7, 2022

Hello @kobelb ,
We are a team of new contributors to your project.
we saw here : [https://www.elastic.co/guide/en/elasticsearch/reference/current/certutil.html]
that certutil already generate pkcs#12 certs, so we want to know more exactly what is the issue and what should we do ?

@GregoireDelahaye GregoireDelahaye mentioned this issue Mar 18, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>enhancement :Security/TLS SSL/TLS, Certificates Team:Security Meta label for security team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rjernst @kobelb @elasticmachine