3 ms·
Basically you can figure out the hash using the aforementioned timing attack. You can now perform an offline attack against the password that produced the hash
by jackjeff 3y ago
Basically you can figure out the hash using the aforementioned timing attack.
You can now perform an offline attack against the password that produced the hash.
It’s like you hacked into the database and got the password hashes.
Then, you fall back to something like hashcat.
If with a bit of luck you just hashed your password with a single round of SHA and did not use something cool like Argon2id then you’re toast. If your password is simple you’re toast too.
On the other hand, if you hashed a totally random key, the safety will rely on whether the hashing algorithm itself is constant time or not. You just moved the needle.
- Nursie 3y ago> Basically you can figure out the hash using the aforementioned timing attack. How are you going to do that?
- theK 3y ago> Basically you can figure out the hash using the aforementioned timing attack. All popular hashing procedures (sha, argon, etc) to my knowledge produce high difference output for small difference inputs. This means that even with one round of sha128[0] your comparison timings turn very erratic. I won't go as far as saying that they turn random, because somebody will jump on it, but what they do achieve is render timing attacks at least impractical for the next few decades. At least to my own knowledge. [0] please don't use sha128!!!