Doc #66366 [Ver->Csd]: Undocumented breaking change, when upgrading from php 5.3
Edit report at https://bugs.php.net/bug.php?id=66366&edit=1
ID: 66366
Updated by: narf@php.net
Reported by: markuwil at gmail dot com
Summary: Undocumented breaking change, when upgrading from
php 5.3
-Status: Verified
+Status: Closed
Type: Documentation Problem
Package: *Encryption and hash functions
PHP Version: Irrelevant
-Assigned To:
+Assigned To: narf
Block user comment: N
Private report: N
New Comment:
The fix for this bug has been committed.
Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
For Windows:
http://windows.php.net/snapshots/
Thank you for the report, and for helping us make PHP better.
Added an entry about this to migration54.incompatible
Previous Comments:
------------------------------------------------------------------------
[2017-03-13 10:19:00] narf@php.net
Automatic comment from SVN on behalf of narf
Revision: http://svn.php.net/viewvc/?view=revision&revision=342107
Log: Fix docs bug #66366: Tiger hash BC not documented in migration54
------------------------------------------------------------------------
[2013-12-29 04:40:33] bjori@php.net
http://us3.php.net/manual/en/function.hash.php#refsect1-function.hash-changelog
Although, you are right, it should have been in the incompatible section too.
------------------------------------------------------------------------
[2013-12-29 04:11:44] markuwil at gmail dot com
Description:
------------
---
From manual page: http://www.php.net/migration54.incompatible
---
Re: https://bugs.php.net/bug.php?id=61291 and
fix regarding Tiger hashes.
This was never documented as a breaking change, when upgrading from 5.3. Also the only changelog
entry related to it cites big endian when the Tiger paper explicitly states little endian. I have no
insight into whether the changelog entry is correct or not but a Tiger hash is little endian whereas
php used to output it in big endian.
To actually get to the root of all of this, one has to, in the worst case, find five years old
reports and then find that they have suddenly been fixed (after first being marked as 'Not a
bug', which implies in-action) without so much as a note in documentation for hash nor mhash
(both of which have suffered from this at one time or another).
Obviously this is breaking change by proxy for anyone who does not know the Tiger specification (and
even appears a bug to anyone who reads Wikipedia, but that is irrelevant to php) or has relied on
the old behavior as correct, to generate, store or compare against hashes such hashes.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=66366&edit=1
Thread (3 messages)