Hacker News new | ask | show | jobs
by qubex 3123 days ago
Following and furthering your logic, what the hell could they have been doing in the codebase to revert a control mechanism that was effective up to and including 10.12.6, but unsafe as of 10.13.0 onwards???
1 comments

A graceful upgrade mechanism towards a new password hashing algorithm.
Change is so, so risky.
There's a lot that can go wrong, which is why writing testable code and then /actually/ testing it, matters so much.