From 0e22f6aedb7723d21094a2a8a577e6b9ea783e05 Mon Sep 17 00:00:00 2001 From: Jonathan Budzenski Date: Tue, 4 Mar 2025 09:35:49 -0600 Subject: [PATCH] [kibana] Remove default OpenSSL legacy provider --- .../kibana-in-production-environments.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/deploy-manage/production-guidance/kibana-in-production-environments.md b/deploy-manage/production-guidance/kibana-in-production-environments.md index db354a5a8e..2080e2d410 100644 --- a/deploy-manage/production-guidance/kibana-in-production-environments.md +++ b/deploy-manage/production-guidance/kibana-in-production-environments.md @@ -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. -