Re:New NIST password guidelines: don't require character typ...
by sleavey on Wednesday December 14, 2016 @01:00PM
(#13178097)
I've seen banks do this, and I agree it's incredibly annoying. KeePassX's autotype function bypasses copy-and-paste restrictions, since it emulates the keyboard as it types your password.
Re:New NIST password guidelines: don't require character typ...
by paulddraper on Thursday December 15, 2016 @01:41AM
(#13182897)
Next is custom screen keyboards made with <canvas>
Re:New NIST password guidelines: don't require character typ...
by chikei on Thursday December 15, 2016 @07:06AM
(#13184011)
You're allow only to input using their custom screen keyboard AND randomize the position of each key.
Banks: this is to prevent attacker use keylogger or mouse position logger.
I was like, are you fucking serious ?
Re:New NIST password guidelines: don't require character typ...
by rolandog on Thursday December 15, 2016 @01:40PM
(#13186959)
Shh... don't give them any ideas.
Re:New NIST password guidelines: don't require character typ...
by nommm-nommm on Wednesday December 14, 2016 @03:51PM
(#13179541)
Pressing F12 and modifying the DOM usually works as well.
Re:New NIST password guidelines: don't require character typ...
by gmiller123456 on Friday December 16, 2016 @10:16AM
(#13193789)
Actually, no. This is about "memorized secrets", not "secrets stored somewhere else". That's not to say that secrets stored somewhere else can't be better than passwords in certain situations, they're just a different type of authentication. A password is "something you know", and stored password is "something you have". Some systems are required to use different types of authentication, one thing you know, one thing you have, and one thing about you (e.g. fingerprint/retina scan). Allowing a copy and paste from a different source violates the "something you know" requirement.
Verifiers SHOULD NOT prevent users from pasting secrets from the keyboard.