Dieser Bereich kann Inhalte enthalten, die nicht für alle Nutzer geeignet sind. Dazu können unter anderem Texte, Medien oder Diskussionen gehören, die als beleidigend, extremistisch, gewaltbezogen oder anderweitig belastend empfunden werden. Wenn du solche Inhalte nicht sehen möchtest, nutze bitte die jeweiligen Filter- und Meldeoptionen der Plattform oder meide entsprechende Threads/Communities.
The article doesn’t clearly explain how all of these fit together, but here’s what I think they mean happens:
Without the “fix” of using another user’s salt, the process would fail immediately for a password-less account. Note that the other user’s salt never plays a role in the calculation because the password is too long and the hash function doesn’t bother calculating it. But it’s the reason execution continues and allows the rest of the bad behaviors to accept the login.
In hindsight, the mistakes are pretty silly. They shouldn’t actually care if the hash matched the user’s hash if they are one the codepath that is only performing the hash to waste time. Long passwords should be rejected earlier as invalid user inputs instead of reaching the hash functions. These decisions are basically saying “I’m going to do something stupid, but it shouldn’t affect anything because the other parts of the code are surely not doing something stupid at the same time”. It’s obvious why this design philosophy didn’t scale.