Skip to content

[kibana] Remove default OpenSSL legacy provider #649

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

Merged
merged 2 commits into from
Mar 22, 2025
Merged

[kibana] Remove default OpenSSL legacy provider #649

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0e22f6a
[kibana] Remove default OpenSSL legacy provider
jbudz Mar 4, 2025
0dce573
Merge branch 'main' into rm-kibana-default-openssl-legacy-provider
eedugon Mar 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions deploy-manage/production-guidance/kibana-in-production-environments.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,9 +106,3 @@ The option accepts a limit in MB:
```js
--max-old-space-size=2048
```


## OpenSSL Legacy Provider [openssl-legacy-provider]

Starting in 8.10.0, {{kib}} has upgraded its runtime environment, Node.js, from version 16 to version 18 and with it the underlying version of OpenSSL to version 3. Algorithms deemed legacy by OpenSSL 3 have been re-enabled to avoid potential breaking changes in a minor version release of {{kib}}. If SSL certificates configured for {{kib}} are not using any of the legacy algorithms mentioned in the [OpenSSL legacy provider documentation](https://www.openssl.org/docs/man3.0/man7/OSSL_PROVIDER-legacy.md), we recommend disabling this setting by removing `--openssl-legacy-provider` in the `node.options` config file.

Loading