Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123835
Message-ID: <e682891f-03e4-45a5-adcc-16ab077358dc@bastelstu.be>
Date: Tue, 25 Jun 2024 20:08:13 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Deprecations for PHP 8.4
To: Rob Landers <rob@bottled.codes>, internals@lists.php.net
References: <bw20I5b7ly3lSbI-2Bv3kfrfTVJbDo5RhwBiQa1PEwuLjprDJWptPajLiaialj1RLVKu7z1j0MofJUhhRVtzT_5i2E11oKeQx_VMUxnKhUE=@gpb.moe>
 <04a480f9-bc8c-4ccc-814d-37316d6e8353@app.fastmail.com>
Content-Language: en-US
In-Reply-To: <04a480f9-bc8c-4ccc-814d-37316d6e8353@app.fastmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 6/25/24 17:39, Rob Landers wrote:
> My only issue is md5, sha1, etc. There are many uses for them besides secure contexts. Sha1 is used by git, md5 fits snuggly in many data structures (uuidv5, for example, though some implementations also use the first 128 bits of a sha1).

I believe you might have misunderstood the proposal. The RFC is not 
proposing the MD5 and SHA-1 *algorithms*. It's just proposing the 
standalone functions.

The algorithms will still be available by means of the hash() function, 
which - besides MD5 and SHA-1 - provides access to a multitude of other 
hash algorithms. The RFC explicitly lists the necessary replacement.

The RFC is just proposing phasing out the special treatment of having 
dedicated functions of MD5 and SHA-1.

Best regards
Tim Düsterhus

PS: git is planning to move away from SHA-1.