Re: [RFC] [VOTE] Deprecations for PHP 8.4
| From: | Tim Düsterhus | Date: | Tue, 30 Jul 2024 19:24:29 +0000 |
| Subject: | Re: [RFC] [VOTE] Deprecations for PHP 8.4 | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-124691@lists.php.net to get a copy of this message | ||
Hi
On 7/28/24 06:33, Mike Schinkel wrote:
P.S. Frankly, I really would not want to see md5() nor sha1() removed because there are valid use-cases for them. I would at least like to see them kept in some form, maybe in anRenaming the functions would do nothing but make this a backwards compatibility break, whereas a deprecation does not. Remember: The algorithms are also available by means of the hash() function (and the related functions), without emitting a deprecation, warning, error, or Exception. Best regards Tim Düsterhus\Insecurenamespace, or renamedinsecure_md5()andinsecure_sha1()or maybe add a third optional bool parameter$insecure_okthat defaults tofalse— or ?enum flag parameter accepting Hashing::INSECURE_OK as its only value — thus allowing developers to explicitly opt-in to insecure use.