Security of cryptographic hash functions: Difference between revisions

Revision as of 19:48, 25 November 2020

Revision as of 07:18, 14 May 2021

Line 19:

===Password case===

Also, if the set of inputs to the hash is relatively small or is ordered by likelihood in some way, then a brute force search may be practical, regardless of theoretical security. Likelihood of recovering the preimage depends on the input set size and the speed or cost of computing the hash function. A common example is the use of hashes to store [[password]] validation data. Rather than store the plaintext of user passwords, an access control system typically stores a hash of the password. When a person requests access, the password they submit is hashed and compared with the stored value. If the stored validation data is stolen, the thief will only have the hash values, not the passwords. However most users choose passwords in predictable ways and often passwords are short enough enough so that all possible combinations can be tested if fast hashes are used.<ref>{{cite web

| url=https://arstechnica.com/information-technology/2012/12/25-gpu-cluster-cracks-every-standard-windows-password-in-6-hours/

| title=25-GPU cluster cracks every standard Windows password in <6 hours