From: Beat Bolli <dev+git@drbeat.li>
To: git@vger.kernel.org
Cc: Xiangfei Ding <xfding@google.com>,
Aniket Gupta <aniketgupta3001@gmail.com>,
Beat Bolli <dev+git@drbeat.li>
Subject: [PATCH v2 1/2] imap-send: use the recommended TLS_method()
Date: Mon, 12 Oct 2026 22:30:56 +0200 [thread overview]
Message-ID: <20261012203057.969878-1-dev+git@drbeat.li> (raw)
In-Reply-To: <20260907211210.2621693-1-dev+git@drbeat.li>
SSLv23_method() has been deprecated since OpenSSL 1.1.0, and
TLS_method() is the recommended function.
Signed-off-by: Beat Bolli <dev+git@drbeat.li>
---
imap-send.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/imap-send.c b/imap-send.c
index bf1d2cf74d..9f21705d77 100644
--- a/imap-send.c
+++ b/imap-send.c
@@ -298,9 +298,9 @@ static int ssl_socket_connect(struct imap_socket *sock,
SSL_library_init();
SSL_load_error_strings();
- meth = SSLv23_method();
+ meth = TLS_method();
if (!meth) {
- ssl_socket_perror("SSLv23_method");
+ ssl_socket_perror("TLS_method");
return -1;
}
--
2.53.0
next prev parent reply other threads:[~2026-10-12 20:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 21:12 [PATCH 0/3] imap-send: future proofing and two correctness fixes Beat Bolli
2026-09-07 21:12 ` [PATCH 1/3] imap-send: prepare for OpenSSL 4.1 Beat Bolli
2026-09-08 4:17 ` Junio C Hamano
2026-09-08 8:26 ` Patrick Steinhardt
2026-09-14 9:10 ` Beat Bolli
2026-09-23 12:32 ` Patrick Steinhardt
2026-09-07 21:12 ` [PATCH 2/3] imap-send: don't expect an ASN1_STRING to be NUL-terminated Beat Bolli
2026-09-08 1:17 ` Junio C Hamano
2026-09-08 8:26 ` Patrick Steinhardt
2026-09-07 21:12 ` [PATCH 3/3] imap-send: only check the CN if no SAN DNS names are present Beat Bolli
2026-09-08 1:28 ` brian m. carlson
2026-10-12 20:30 ` Beat Bolli [this message]
2026-10-12 20:30 ` [PATCH v2 2/2] imap-send: let OpenSSL do the hostname verification Beat Bolli
2026-10-12 22:00 ` Aniket Gupta
2026-10-13 13:14 ` Patrick Steinhardt
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=20261012203057.969878-1-dev+git@drbeat.li \
--to=dev+git@drbeat.li \
--cc=aniketgupta3001@gmail.com \
--cc=git@vger.kernel.org \
--cc=xfding@google.com \
/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