4 ms·
>If you can keep attackers from learning a "pepper", keep the attackers from learning the password hashes too. Problem solved. Isn't it easier to protect one p
by pbhjpbhj 14y ago
>If you can keep attackers from learning a "pepper", keep the attackers from learning the password hashes too. Problem solved.
Isn't it easier to protect one password than protect millions that have to be connected somehow to an internet connected database.
Your pepper could be completely off-internet requiring physical access. That's not likely to be true of your password hashes. You'd likely have to wait a couple of days to get an account verified this way so that passwords submitted could be physically moved to the "pepper pot" [I made that up] and peppered and hashed codes could be returned.
"If you can take one step, why can't you take 10 million? Problem solved."
Tenability of such a scheme could vary!
- tptacek 14y agoNo, your "pepper" cannot be completely off-internet requiring physical access, since it's required to actually validate an incoming password submission against the password hash.
- pbhjpbhj 14y ago"Tenability of such a scheme could vary!"
- tptacek 14y agoI believe the tenability of your scheme varies from "unpossible" to "suitable for sites with such low traffic that the sysadmin can manually verify every login".
- egsec 14y agoIf you are running it through an HSM, wouldn't that accomplish this goal? Take a code, encrypt with HSM, then do hashing, etc. You would have to hack the server then compromise the HSM in order to do an offline attack.