Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124597
Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecations for PHP 8.4
To: internals@lists.php.net
References: <USzt7tZZlO1DmAbSTLhD-bqa23FqZn0zk2aah8Ndxgk9c7RY5PefQ8MjbYPUYAzr2_m4Cf-5AI4PuNBTS84rim_FNS6RaT-cWSv714HEvvU=@gpb.moe>
 <1a88918e-e808-d778-45e1-53797660e093@php.net>
 <CAPrKfG5Cw_nU7g7FR+t4C1-YZ8CDsDO_-sRs=yEsHO5kCTZL+A@mail.gmail.com>
 <c03eb187-bd21-4a4b-9faf-8d0243eaa994@varteg.nz>
 <aa6bc7aa-28d9-40ca-974f-65075adb6199@rwec.co.uk>
 <9041cba85d6439682bb44fcb29210c944dbe3911.camel@ageofdream.com>
Message-ID: <66A2D544.5060801@adviesenzo.nl>
Date: Fri, 26 Jul 2024 00:44:20 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <9041cba85d6439682bb44fcb29210c944dbe3911.camel@ageofdream.com>
Content-Type: multipart/alternative;
 boundary="------------050208030204020608000304"
From: php-internals_nospam@adviesenzo.nl (Juliette Reinders Folmer)

This is a multi-part message in MIME format.
--------------050208030204020608000304
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 26-7-2024 0:00, Nick Lockheart wrote:
>
> That's a good point. What if there were crypto functions that worked
> like password_hash() in that they had one generic function name, but
> magically used the new/better "best practice" algorithms as time went
> by without the need to update any calling code?
>
> Maybe there should be three generic-named functions:
>
> fast_hash() // not secure, makes UIDs quickly
> secure_hash() // uses best practice one-way hash algo
> secure_crypt() // uses best practice reversible encryption.

While I like the idea, this sounds like a huge nightmare in the waiting 
when data is stored somewhere and later compared.

Example:
* Let's say these functions get introduced in PHP 8.5.
* `secure_hash()` is used in an application running on PHP 8.5 to secure 
some data before storing it in a database. This data is used in 
comparisons - stored vs user provided.
* Now in PHP 9.1, the hash algorithm is changed.
* The production environment gets updated to PHP 9.1 and suddenly the 
application breaks as the data verification will no longer work as the 
new algo is used on the user provided data, but the database stored 
version of the same data was created with the old algo....


--------------050208030204020608000304
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 26-7-2024 0:00, Nick Lockheart
      wrote:<br>
    </div>
    <blockquote
      cite="mid:9041cba85d6439682bb44fcb29210c944dbe3911.camel@ageofdream.com"
      type="cite"><br>
      <pre wrap="">That's a good point. What if there were crypto functions that worked
like password_hash() in that they had one generic function name, but
magically used the new/better "best practice" algorithms as time went
by without the need to update any calling code?

Maybe there should be three generic-named functions:

fast_hash() // not secure, makes UIDs quickly
secure_hash() // uses best practice one-way hash algo
secure_crypt() // uses best practice reversible encryption.
</pre>
    </blockquote>
    <br>
    While I like the idea, this sounds like a huge nightmare in the
    waiting when data is stored somewhere and later compared.<br>
    <br>
    Example:<br>
    * Let's say these functions get introduced in PHP 8.5.<br>
    * `secure_hash()` is used in an application running on PHP 8.5 to
    secure some data before storing it in a database. This data is used
    in comparisons - stored vs user provided.<br>
    * Now in PHP 9.1, the hash algorithm is changed.<br>
    * The production environment gets updated to PHP 9.1 and suddenly
    the application breaks as the data verification will no longer work
    as the new algo is used on the user provided data, but the database
    stored version of the same data was created with the old algo....<br>
    <br>
  </body>
</html>

--------------050208030204020608000304--