From a7816c9600b76ee0905ad35c7baa435a982a7c7f Mon Sep 17 00:00:00 2001 From: Matt Caswell Date: Fri, 4 Apr 2025 10:12:46 +0100 Subject: [PATCH] Fix a reference in the OpenSSL guide to QUIC for servers MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit One part of the OpenSSL guide suggests we only support clients for QUIC which is no longer true. Reviewed-by: Saša Nedvědický Reviewed-by: Tomas Mraz Reviewed-by: Tim Hudson Reviewed-by: Neil Horman (Merged from https://github.com/openssl/openssl/pull/27265) (cherry picked from commit 0a16bb7e740306a10c14a6f92c42782f9b5e2048) --- doc/man7/ossl-guide-libssl-introduction.pod | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/man7/ossl-guide-libssl-introduction.pod b/doc/man7/ossl-guide-libssl-introduction.pod index 3c1a5d73837..81e2fa891bd 100644 --- a/doc/man7/ossl-guide-libssl-introduction.pod +++ b/doc/man7/ossl-guide-libssl-introduction.pod @@ -67,7 +67,7 @@ that an application may need to use. They are summarised below. This structure is used to indicate the kind of connection you want to make, e.g. whether it is to represent the client or the server, and whether it is to use -SSL/TLS, DTLS or QUIC (client only). It is passed as a parameter when creating +SSL/TLS, DTLS or QUIC. It is passed as a parameter when creating the B. =item B (SSL Session) -- 2.47.2