Skip to content

Document that Endpoint does not support Elliptic Curve keys for SSL #1133

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

Open
ferullo opened this issue Apr 14, 2025 · 4 comments
Open

Document that Endpoint does not support Elliptic Curve keys for SSL #1133

ferullo opened this issue Apr 14, 2025 · 4 comments
Assignees
Labels
Team:Security Issues owned by the Security Docs Team

Comments

@ferullo
Copy link

ferullo commented Apr 14, 2025

What can we change to make the docs better?

Endpoint does not support Elliptic Curve keys for SSL certificates. It silently discards them (since it can't use them) which makes debugging hard. We should document that it doesn't support them, especially because Agent and Beats do.

Doc URL

This page might be a good place to mention it? https://www.elastic.co/guide/en/security/current/elastic-endpoint-deploy-reqs.html Or start a new page?

Which documentation set needs improvement?

ESS and serverless

Software version

This affects all Endpoint versions.

@ferullo
Copy link
Author

ferullo commented Apr 14, 2025

@jmikell821 jmikell821 transferred this issue from elastic/security-docs Apr 14, 2025
@jmikell821 jmikell821 added the Team:Security Issues owned by the Security Docs Team label Apr 14, 2025
@intxgo
Copy link

intxgo commented Apr 28, 2025

Agree, we should document it until we add such support. Just a minor remark: since v8.16.0 it's no longer silent, policy response indicates failure "Unsupported or invalid PEM format".

@111andre111
Copy link

However that message is in my opinion still a little too vague, if we could make that message more clear, that would help a lot.

@intxgo
Copy link

intxgo commented Apr 29, 2025

However that message is in my opinion still a little too vague, if we could make that message more clear, that would help a lot.

the problem is that until endpoint can handle EC keys, it doesn't know if it's an EC key, to make the message more specific. Furthermore, we support PEM injected directly as the node value, or a path to it pointing somewhere in a local FS, that adds additional complexity with trying to give more specific messages. With the policy response UI in Kibana as it is, we don't want to inject the whole text value because PEM content is quite big and multiline

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Security Issues owned by the Security Docs Team
Projects
None yet
Development

No branches or pull requests

5 participants