in reply to
Re^2: 5.18.0 is available NOW!
in thread 5.18.0 is available NOW!
How isn't this a good reason?
That is not the problem; the response to that is.
When considering a breaking change, I was taught to ask three questions:
Is the thing being 'fixed' actually manifesting itself in production code.
Has any real-world occurrence of the ACA actually been witnessed or reported?
Either by limiting the total breakage; or by selectively applying the breaking fix only when required.
Could the 'fix' have been limited to (say) only when taint was enabled?
Not the first. Not the best. Not the least effort or least worst; but the ONLY?
Is it necessary to randomise all hashes differently?
Wouldn't picking the same random hash initialisation, for all hashes for any given run, have been just as effective at stopping real-world exploits in the wild?
Wrong on every count. And posting anonymously proves it.
Where is the proof of concept code? (Without it, this is nothing more that idle speculation that has cost a lot of people a lot of time and effort.)
Used as intended
The most useful key on my keyboard
Used only on CAPS LOCK DAY
Never used (intentionally)
I don't use a keyboard
Results (2 votes),