Re:Short session expiration does not help security
by rrrpfb11 on Friday August 18, 2023 @11:56AM
(#37177467)
Re single positions, my bank requires a password (which one hopes is appropriately hashed and so forth) plus a challenge to supply requested offsets into a secret phrase. That mitigates I suppose against over the shoulder attack. And they have fewer requirements of the phrase so maybe it’s less likely to be written down?
I’m curious whether there’s a technical means to allow the challenge by offset without storing the phrase plain text. I’m challenged for four positions - in theory it could store hashes of all possible four offsets, but is there a better way?
Re:Short session expiration does not help security
by GoblinSlayer on Friday August 18, 2023 @12:49PM
(#37178396)
Split the secret into characters then compute verifier bytes for each character:
verifier[i]=hash(pepper,salt,i,secret[i])[0]
I find that bank websites usually follow completely opposite ways regarding to security than any other industry: very short passwords, only digits, not encrypted in db (some sites ask for single positions), mandatory password input by virtual keyboard, cannot use password managers, not using 2FA or only allowing SMS instead of TOTP or other methods, etc...