Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120212
Return-Path: <phpdev@ehrhardt.nl>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 59506 invoked from network); 8 May 2023 11:15:36 -0000
Received: from unknown (HELO localhost.localdomain) (76.75.200.58)
  by pb1.pair.com with SMTP; 8 May 2023 11:15:36 -0000
To: internals@lists.php.net
Date: Mon, 08 May 2023 13:15:34 +0200
Message-ID: <1bmh5il09q2gsou20ru8r72am20cgnoa79@4ax.com>
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)

"Christoph M. Becker" in php.internals (Wed, 18 Jan 2023 13:20:41 +0100):
>Hi all!
>
>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).

I do not mind, but I just noticed that even the official PHP 8.1.19 RC1
still ships with OpenSSL 1.1.1. What is the status?
-- 
Jan