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

Update Documentation - TLS configuration of the Elastic Package Registry #1279

Closed
kharsalan opened this issue Aug 30, 2024 · 4 comments · Fixed by #1280
Closed

Update Documentation - TLS configuration of the Elastic Package Registry #1279

kharsalan opened this issue Aug 30, 2024 · 4 comments · Fixed by #1280

Comments

@kharsalan
Copy link

kharsalan commented Aug 30, 2024

Request to update This doc which includes information about TLS configuration of the Elastic Package Registry. However, we don't see anything specific about the TLS version settings.

To force >= 1.2, Package Registry needs to be run with EPR_TLS_MIN_VERSION=1.2.

@kpollich kpollich transferred this issue from elastic/package-registry Sep 3, 2024
@kpollich
Copy link
Member

kpollich commented Sep 3, 2024

@kilfoyle - FYI I transferred this from package-registry to ingest-docs. @jsoriano can you confirm the above note about TLS versions is relevant + accurate and add anything else that we might need to get these docs updated?

@jsoriano
Copy link
Member

jsoriano commented Sep 3, 2024

We might say that Package Registry supports min TLS from 1.0 to 1.3, and defaults to 1.0.
In the next release the default will change to 1.2. It relies for defaults on the Go implementation https://pkg.go.dev/crypto/tls#Config.

@kilfoyle
Copy link
Contributor

kilfoyle commented Sep 3, 2024

Thanks @jsoriano! I've opened #1280 to add this to the docs.

In the next release the default will change to 1.2.

Will this be for 8.16? If so, I'll open a separate PR for that.

@kilfoyle
Copy link
Contributor

kilfoyle commented Sep 3, 2024

@kharsalan Thanks for reporting this! The page you mentioned will be updated via #1280

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

Successfully merging a pull request may close this issue.

4 participants