> It'd be worse to keep the wrong behavior, providing as tiger what it is not. > What can be done is to add a "tiger192,3-broken php5.4" hash for BC of > those which may have used the new one. > It's serious enough so I'd consider it a factor for a new minor in short > time, but not for setting in stone a wrong behavior.
wat? The new hashes are correct. I'm awfully sorry that there has been so much trouble with the tiger hashes, but it happened and cannot be undone. -- Regards, Mike -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
