Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108445 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 85847 invoked from network); 11 Feb 2020 00:22:24 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 11 Feb 2020 00:22:24 -0000 To: internals@lists.php.net References: Date: Mon, 10 Feb 2020 22:36:09 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 94.8.17.105 Subject: Re: [RFC] deprecate md5_file and sha1_file From: marandall@php.net (Mark Randall) Message-ID: On 10/02/2020 21:49, Tom Van Looy via internals wrote: > I suggest to deprecated the functions md5_file() and sha1_file(). This will > make people think about upgrading to a better alternative. It won't. At best it will make people switch to the hash function. At worst people will not upgrade. If people are using the existing md5 / sha1 algorithms, chances are it's because they're actually wanting to get a hash to compare to something that has already been stored. There's not much point in deprecating the algorithm if we don't eventually plan to remove it, and there is an exactly zero percent chance of it being removed at any point in the next 50 years. Mark Randall