Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108446 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 87749 invoked from network); 11 Feb 2020 00:28:34 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Feb 2020 00:28:34 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 3DEF91804E6 for ; Mon, 10 Feb 2020 14:42:18 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-vk1-f170.google.com (mail-vk1-f170.google.com [209.85.221.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 10 Feb 2020 14:42:17 -0800 (PST) Received: by mail-vk1-f170.google.com with SMTP id w4so2380179vkd.5 for ; Mon, 10 Feb 2020 14:42:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0LYkUHURRboFmdCriQDEaGib9+URe8PobxfJXVvwMiU=; b=lBB6AdXbXH5iG31sT0tVpn6/9seziqzDgvFkW5u0hPyemMJQ+dE8qfZM8GEJ1JNij7 RnH7UcPqfTPTtjVXfvo5rJHcCOnCFHy6DxZ+halLhSjzZsy6gWfeWVXcQ4Gk8SUzOeIC xtgsnU5w3kaiDnAiW+dGsCDCzXW+xdIbrxAGau0IySnGErvMA/QLzz3ukePB7vEi/8ki qCUXn8+9juVOKUxzXyNdGl7repHxXjSQ38MayjiDPnHYQRItMZHAtJvidnCTdSXzwj45 0jtPmCzR/vtWN8Nt0Pt0cwPVq5KS8VXv0zR0uDAUq3pv0BcCEpKnaCZ1asJm+yxJKwYv iqvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0LYkUHURRboFmdCriQDEaGib9+URe8PobxfJXVvwMiU=; b=XLmaBXaE3KWF91/nd9UqbadhzbCxWuy9no7/miJ5otwT4UVXzaE3wy3QxxJZwBRctw f0Sqg1R7BT8CqB/XOFqb9d3tXWum3Qm0fo5wkSsIXfq4S09Fb695M7Pv7ms5bmgU8bBE m6h3uhfn1eHNmJyeBAzb8HVzlxkMjcUPrNaSDo4TxQac4AC8dteYwulBdjMwG1s5VCt3 9g/KSvQ921KWDntn408dOYe5a7kpAUkIaWRrUS0ewK/NDBrz4a0GcWiK0Zb824YBVMoI lwrZQXz3UPfWvyegVE1LOL9yuCCP8KiXMPMBr/UtxU5W5OPsaNJNj1Pym6Tlz4w/RtNY ddvA== X-Gm-Message-State: APjAAAWF4Tn/RTWOkpOC334h+UD9j/4pZb3hNqbMX5K+PLvY6Xa/hdmb /TrqtwlPYK8Lg8wIr09F/d8spt1SUOwnnROhoQJCiA== X-Google-Smtp-Source: APXvYqxiEcGBRjxAivHFN/lmJ/aF+KloGwx0ojxTMe+2tliAK5+ukP3C5o20Ff+fd0VeoJydgtrzN0nq+dTHiBLHgxc= X-Received: by 2002:ac5:c9a8:: with SMTP id f8mr2771880vkm.10.1581374536875; Mon, 10 Feb 2020 14:42:16 -0800 (PST) MIME-Version: 1.0 References: <5e41dadc.1c69fb81.a6614.77f0SMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: <5e41dadc.1c69fb81.a6614.77f0SMTPIN_ADDED_MISSING@mx.google.com> Date: Mon, 10 Feb 2020 17:42:05 -0500 Message-ID: To: Mark Randall Cc: PHP internals Content-Type: multipart/alternative; boundary="0000000000008702b2059e4073d0" Subject: Re: [PHP-DEV] Re: [RFC] deprecate md5_file and sha1_file From: chasepeeler@gmail.com (Chase Peeler) --0000000000008702b2059e4073d0 Content-Type: text/plain; charset="UTF-8" On Mon, Feb 10, 2020 at 5:36 PM Mark Randall wrote: > 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 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > Why? What does deprecating those two functions do to make PHP a better language? It doesn't add any new features. It doesn't fix any security issues. It doesn't even take away the ability to perform the functionality that they provide, since it still exists in the hash_file function. If you don't like the function, then don't use it. -- Chase Peeler chasepeeler@gmail.com --0000000000008702b2059e4073d0--