Re:Okta – Username Above 52 Characters Security Advisory
by lmz on Saturday November 02, 2024 @01:24AM
(#42024239)
No. Such a rainbow table is per-username and non reusable. Which is the point of salting.
[ Parent
| on HN ]
Re:Okta – Username Above 52 Characters Security Advisory
by heliosyne on Saturday November 02, 2024 @02:08AM
(#42024359)
No, rainbow tables are hash-input specific. They're user-specific only if the salt is user-unique. Usernames aren't normally part of the hash input because they're assumed-public knowledge.
You can test this for yourself by creating a user account, then editing the master password database and manually changing the username without recalculating the password hash. The password will still work. If the username was part of the hash input, the password would fail.
Re:Okta – Username Above 52 Characters Security Advisory
by lmz on Saturday November 02, 2024 @05:10AM
(#42025065)
You complained about them salting using the public username as salt. You asserted that this makes the rainbow table computable offline. I asserted that this didn't matter much for security since the table for H(username || secret) is username specific and not reusable for other usernames. Since precomputed rainbow tables consume quite a bit of space it is rather unlikely that anyone would have such a table stored for any random username.
Re:Okta – Username Above 52 Characters Security Advisory
by heliosyne on Saturday November 02, 2024 @07:09AM
(#42025615)
I didn't complain about anyone. The Okta vulnerability isn't because of public salts.
Re:Okta – Username Above 52 Characters Security Advisory
by vlovich123 on Saturday November 02, 2024 @11:42AM
(#42027048)
You can still build a rainbow table for a specific username if you want to do a targeted attack.