Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120565 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 73364 invoked from network); 13 Jun 2023 20:06:50 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 13 Jun 2023 20:06:50 -0000 To: internals@lists.php.net Date: Tue, 13 Jun 2023 22:06:46 +0200 Message-ID: References: <989f473a-010b-5a2b-017c-f8fb00467c14@gmx.de> X-Newsreader: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Posted-By: 77.174.241.57 Subject: Re: PHP 8.1 and OpenSSL From: phpdev@ehrhardt.nl (Jan Ehrhardt) Hi Christoph, "Christoph M. Becker" in php.internals (Wed, 18 Jan 2023 13:20:41 +0100): >While the official builds for PHP 8.2 already use OpenSSL 3.0, the PHP >8.1 builds are still using OpenSSL 1.1.1. However, OpenSSL 1.1.1 is >only supported till 2023-09-11[1], while PHP 8.1 is supported till >2024-11-25[2]. Although I don't like bumping the OpenSSL version in the >middle of PHP 8.1's lifetime, I suppose it is necessary to avoid falling >behind security support. And if we do that bump, we better do it sooner >than later. > >So, if there are no unforeseen problems, I suggest to build PHP >8.1.16RC1 with OpenSSL 3.0 (PHP 8.1.15RC1 has already been built with >OpenSSL 1.1.1). > >Thoughts? Objections? > >[1] >[2] I noticed that PHP 8.1.20 at https://windows.php.net/download/ was built with OpenSSL 1.1.1t and PHP 8.2.7 & 8.3.0 Alpha 1 with OpenSSL 3.0.8. What will be the official policy for 8.1, 8.2 and 8.3? All 3 versions with OpenSSL 3.0.x or 8.1 still with OpenSSL 1.1.1? And none of the three versions with OpenSSL 3.1.x? Please clarify. -- Jan