Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108441 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 75953 invoked from network); 10 Feb 2020 23:36:20 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 10 Feb 2020 23:36:20 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 3E2801804E6 for ; Mon, 10 Feb 2020 13:50:04 -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=-0.2 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,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-qv1-f48.google.com (mail-qv1-f48.google.com [209.85.219.48]) (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 13:50:03 -0800 (PST) Received: by mail-qv1-f48.google.com with SMTP id dc14so3975865qvb.9 for ; Mon, 10 Feb 2020 13:50:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ctors.net; s=google; h=mime-version:from:date:message-id:subject:to; bh=WmtobC6VFLBy5RCbgIsBuQgpFnxP+mQi3S/6SpzvrM8=; b=krqkUMvLb4ga9EwwNIzcYgFFKOL7t+YhxB5he37jOqtcy1PCJTdUmfmzZmMrLlUTIn LsbV62uq5X73Rks0guTrqoufdcD8hq2iNT1tLdqUhGAaFqwfYN3uZQiUm5Oboj+abKh7 +j2eBuVzHN/45fojc/4Vo0MVAR6eLLmDPSbLUVqR0Fhljspiw6GQdQr5X7yKWN6VcIvo NfELZmAVPOI/h2U6LvaNT+oVc+tfFCtcGAlSrS3q/bHg22kb8xT7h9YFPRw0wg5lUbXm 4UHvoZoiORAHDz29elgzvHUVZYxNZkT97GelNzG71Wcdprg8MmMc9MT1fKkFi42b8pes N3BA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=WmtobC6VFLBy5RCbgIsBuQgpFnxP+mQi3S/6SpzvrM8=; b=XiAdDqa9nMu11rWzHsIF5Gki0TYScv2OgiZF4ICvzafJwUUDfWjssGKc0n2tv05jeF 7Wfuh/xTg2+QNeerwwCF91U2mCFMflRr+OXT5D8vretHtqhQwnwyvmcQox2725giJBhT lok1TZGWtZ1CYI0fEDEB02TU9ffMFk5Wc7+D2HcIT9sMu6mvWqBmWbPmMjPrUWgj7GZt uUpTvYPD8Pw9//I+xDBFjjTyxZWTgmT7gfmfJJqZ0wsIVYGEJNzUeEJ7Iq14GgNIUaEj RxZLxUZpBpXoJlNkqdb9L6uY8sMb7vOBjyxWTEIqvM72EWaIaErFvFIU7WufXkHOPMRp NyXQ== X-Gm-Message-State: APjAAAULbgkvM6F7xAntbNAlyWrgDTsfSCU8RW/SQrCFsFokpt8tNkHM CZMWToWeunk6Gx1qUR5+5N2gIPPvv7h5y86lq1op+3gcj9c= X-Google-Smtp-Source: APXvYqwXAeATG9Y65U9HcMYDJVQIwQuFAA0ABDz4THelkfeMj/C9ZaSFlzZQMGpbZK2E3ukTCnjSxI9seVkWr0BsYYw= X-Received: by 2002:a05:6214:1494:: with SMTP id bn20mr12341158qvb.43.1581371402252; Mon, 10 Feb 2020 13:50:02 -0800 (PST) MIME-Version: 1.0 Reply-To: Tom Van Looy Date: Mon, 10 Feb 2020 22:49:51 +0100 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="000000000000b086dd059e3fb838" Subject: [RFC] deprecate md5_file and sha1_file From: internals@lists.php.net ("Tom Van Looy via internals") --000000000000b086dd059e3fb838 Content-Type: text/plain; charset="UTF-8" Hi While in some environments the use of MD5 and SHA1 are still acceptable for some use cases like file integrity verification etc. the use of these algorithms should be discouraged and not be your choice when developing new applications. I suggest to deprecated the functions md5_file() and sha1_file(). This will make people think about upgrading to a better alternative. If you still need this functionality you can always switch to the hash_file() function. Carrying around these two dedicated functions seems a bit too much for a modern PHP. What do you think? My feeling was that this is a no brainer. Should I open an RFC for this? Kind regards, Tom Van Looy --000000000000b086dd059e3fb838--