public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Tomas Mraz <tmraz@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/openssl] rebase_40beta: Unused patch dropped
Date: Tue, 09 Jun 2026 12:44:44 GMT [thread overview]
Message-ID: <178100908408.1.5952126327181822224.rpms-openssl-d902645d90be@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/openssl
Branch : rebase_40beta
Commit : d902645d90bea1318741181dae5c88da74bcddd7
Author : Tomas Mraz <tmraz@fedoraproject.org>
Date : 2020-05-18T13:13:56+02:00
Stats : +0/-36 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/openssl/c/d902645d90bea1318741181dae5c88da74bcddd7?branch=rebase_40beta
Log:
Unused patch dropped
---
diff --git a/openssl-1.1.1-status-request.patch b/openssl-1.1.1-status-request.patch
deleted file mode 100644
index 3f92cd5..0000000
--- a/openssl-1.1.1-status-request.patch
+++ /dev/null
@@ -1,36 +0,0 @@
-From 93e26cedac20844733d59f33e313880da17fa23a Mon Sep 17 00:00:00 2001
-From: Matt Caswell <matt@openssl.org>
-Date: Thu, 5 Sep 2019 16:43:57 +0100
-Subject: [PATCH 1/2] Don't send a status_request extension in a
- CertificateRequest message
-
-If a TLSv1.3 server configured to respond to the status_request extension
-also attempted to send a CertificateRequest then it was incorrectly
-inserting a non zero length status_request extension into that message.
-
-The TLSv1.3 RFC does allow that extension in that message but it must
-always be zero length.
-
-In fact we should not be sending the extension at all in that message
-because we don't support it.
-
-Fixes #9767
----
- ssl/statem/extensions_srvr.c | 4 ++++
- 1 file changed, 4 insertions(+)
-
-diff --git a/ssl/statem/extensions_srvr.c b/ssl/statem/extensions_srvr.c
-index e16722cbeb8..1c023fc6c40 100644
---- a/ssl/statem/extensions_srvr.c
-+++ b/ssl/statem/extensions_srvr.c
-@@ -1491,6 +1491,10 @@ EXT_RETURN tls_construct_stoc_status_request(SSL *s, WPACKET *pkt,
- unsigned int context, X509 *x,
- size_t chainidx)
- {
-+ /* We don't currently support this extension inside a CertificateRequest */
-+ if (context == SSL_EXT_TLS1_3_CERTIFICATE_REQUEST)
-+ return EXT_RETURN_NOT_SENT;
-+
- if (!s->ext.status_expected)
- return EXT_RETURN_NOT_SENT;
-
reply other threads:[~2026-06-09 12:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178100908408.1.5952126327181822224.rpms-openssl-d902645d90be@fedoraproject.org \
--to=tmraz@fedoraproject.org \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox