From 491cf67ce2268e0e8781d373c080f4bfd3a354a8 Mon Sep 17 00:00:00 2001 From: ewen Date: Tue, 13 Aug 2024 00:01:05 +0000 Subject: [PATCH] Added a comment: Most servers upgraded to TLS v1.2 EMS / TLS v1.3 --- ...ent_2_496491402d56c71288db3c209e4248d6._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/tls__58___peer_does_not_support_Extended_Main_Secret/comment_2_496491402d56c71288db3c209e4248d6._comment diff --git a/doc/bugs/tls__58___peer_does_not_support_Extended_Main_Secret/comment_2_496491402d56c71288db3c209e4248d6._comment b/doc/bugs/tls__58___peer_does_not_support_Extended_Main_Secret/comment_2_496491402d56c71288db3c209e4248d6._comment new file mode 100644 index 0000000000..86850759f7 --- /dev/null +++ b/doc/bugs/tls__58___peer_does_not_support_Extended_Main_Secret/comment_2_496491402d56c71288db3c209e4248d6._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="ewen" + avatar="http://cdn.libravatar.org/avatar/605b2981cb52b4af268455dee7a4f64e" + subject="Most servers upgraded to TLS v1.2 EMS / TLS v1.3" + date="2024-08-13T00:01:05Z" + content=""" +For the record, this problem has largely \"solved itself\" by waiting -- one of the podcast feeds I was having problems with upgraded to a new server (ie, off CentOS 7 I think), which supports TLS v1.3, so is no longer a problem. And around the end of support for CentOS 7 (~ June 2024) the other problem server also stopped being a problem, I'm guessing due to deploying new media servers. + +Among other things this means I no longer have a good test case to suggest for testing this problem. + +So possibly the problem of \"TLS v1.2 EMS now required\" can be ignored, because at this point it should largely be very old (unmaintained) server installs that still cannot do TLS v1.2 EMS or TLS v1.3 + +Ewen +"""]]