From 377cdb0935dfd69c60475aae98e109ec6259fc13 Mon Sep 17 00:00:00 2001 From: Andre Klapper Date: Thu, 25 Sep 2025 17:40:04 +0200 Subject: [PATCH] Diviner: Remove coverage of a 15 year old SNI problem Summary: OpenSSL 1.0.0 was released in March 2010 and saw its End of Life in 2016. Test Plan: None. Reviewers: O1 Blessed Committers, mainframe98 Reviewed By: O1 Blessed Committers, mainframe98 Subscribers: tobiaswiese, valerio.bozzolan, Matthew, Cigaryno Differential Revision: https://we.phorge.it/D26377 --- .../configuration/troubleshooting_https.diviner | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/src/docs/user/configuration/troubleshooting_https.diviner b/src/docs/user/configuration/troubleshooting_https.diviner index b3aae81035..b76a0958e6 100644 --- a/src/docs/user/configuration/troubleshooting_https.diviner +++ b/src/docs/user/configuration/troubleshooting_https.diviner @@ -65,16 +65,4 @@ topic is complicated, but you can test for it by running: $ openssl s_client -connect example.com:443 -servername example.com -Replace **both** instances of "example.com" with your domain. If you receive -an error in `SSL23_GET_SERVER_HELLO` with `reason(1112)`, like this: - - CONNECTED(00000003) - 87871:error:14077458:SSL routines:SSL23_GET_SERVER_HELLO:reason(1112): - /SourceCache/OpenSSL098/OpenSSL098-44/src/ssl/s23_clnt.c:602: - -...it indicates server is misconfigured. The most common cause of this problem -is an Apache server that does not explicitly name the Phorge domain as a -valid VirtualHost. - -This error occurs only for some versions of the OpenSSL client library -(from v0.9.8r or earlier until 1.0.0), so only some users may experience it. +Replace **both** instances of "example.com" with your domain. -- 2.54.0