Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124586
Precedence: bulk
MIME-Version: 1.0
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>
In-Reply-To: <c03eb187-bd21-4a4b-9faf-8d0243eaa994@varteg.nz>
Date: Wed, 24 Jul 2024 22:33:28 -0700
Message-ID: <CAPrKfG5LTRMihSunFiLS7FQYNTEg4nuKDYsMQAjaQK2zMXebKw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecations for PHP 8.4
To: Morgan <weedpacket@varteg.nz>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000b0833e061e0bbcb1"
From: sarkedev@gmail.com (Peter Stalman)

--000000000000b0833e061e0bbcb1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 24, 2024 at 3:03=E2=80=AFPM Morgan <weedpacket@varteg.nz> wrote=
:

> And they would still be available as hash("md5") and hash("sha1"); the
> only reason they're called out as their own distinct functions today is
> historical inertia.
>

Yes, I am aware of that, it's covered in the RFC and has been discussed.
My issue is that I think the positive effect this will have is minimal,
while the impact is very extensive.  I also disagree with the notion that
there is no longer a use for these algos in the present day, as there are
many technologies and systems that still use these for basic checksumming.
To make everyone go through and update these seems ridiculous to me, as
it's basically just **renaming functions**.  If it goes through, I
foresee a composer package called md5-sha1-shim being a popular package.
It won't stop the people this intends to save.

Lots of effect with little gain.  The warning in the documentation should
be sufficient.

Thanks,
Peter

--000000000000b0833e061e0bbcb1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Jul 24, 2024 at 3:03=E2=80=AFPM M=
organ &lt;<a href=3D"mailto:weedpacket@varteg.nz">weedpacket@varteg.nz</a>&=
gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">
And they would still be available as hash(&quot;md5&quot;) and hash(&quot;s=
ha1&quot;); the <br>
only reason they&#39;re called out as their own distinct functions today is=
 <br>
historical inertia.<br></blockquote><div><br></div><div>Yes, I am aware of =
that, it&#39;s covered in the RFC and has been discussed.=C2=A0 My issue is=
 that I think the positive effect this will have is minimal, while the impa=
ct is very extensive.=C2=A0 I also disagree with the notion that there is n=
o longer a use for these algos in the present day, as there are many techno=
logies and systems that still use these for basic checksumming. To make eve=
ryone go through and update these seems ridiculous=C2=A0to me, as it&#39;s =
basically just **renaming=C2=A0functions**.=C2=A0 If it goes through, I for=
esee=C2=A0a composer package called md5-sha1-shim being a popular package.=
=C2=A0 It won&#39;t stop the people this intends to save.</div><div><br></d=
iv><div>Lots of effect with little gain.=C2=A0 The warning in the documenta=
tion=C2=A0should be sufficient.</div><div><br></div><div>Thanks,</div><div>=
Peter</div><div><br></div></div></div>

--000000000000b0833e061e0bbcb1--