Path: ...!news.misty.com!.POSTED.veps.esmtp.org!not-for-mail
From: Claus =?iso-8859-1?Q?A=DFmann?= <INVALID_NO_CC_REMOVE_IF_YOU_DO_NOT_POST_ml+sendmail(-no-copies-please)@esmtp.org>
Newsgroups: comp.mail.sendmail
Subject: Re: OpenSSL 3.4.x supported?
Date: Tue, 7 Jan 2025 01:28:38 -0500 (EST)
Organization: MGT Consulting
Sender: <ml+sendmail(-no-copies-please)@esmtp.org>
Message-ID: <vlihim$gin$1@news.misty.com>
References: <vknu9u$4th9$1@dont-email.me> <vlfspb$1g6rm$1@dont-email.me> <vlgvo9$k4g$1@news.misty.com> <vlhslc$rr3$1@tncsrv09.home.tnetconsulting.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 7 Jan 2025 06:28:38 -0000 (UTC)
Injection-Info: news.misty.com; posting-host="veps.esmtp.org:155.138.203.148";
	logging-data="16983"; mail-complaints-to="abuse@misty.com"
Mail-Copies-To: never
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: ca@x2.esmtp.org (Claus Assmann)
Bytes: 1613
Lines: 14

Grant Taylor  wrote:

> Which would mean that if the defaults compiled into OpenSSL change, then 
> Sendmail's behavior might also unexpectedly change.

If you use different code, then you get different behaviour.
Hence it might be a good idea to read the "change log"
(and hope that all relevant changes are properly documented).

> The thing that comes to mind is the OpenSSL team changing what ciphers / 
> algorithms / key lengths / etc. are set as the default in the compiled 
> library.

Let's hope the RFCs are followed - after all, this is about
interoperability.