Ask HN: Disabling paste in password boxes - why is it practiced?
The justification by the app builders is that it "improves security". I dont buy it.
Is there a good reason to disable this functionality? What does it improve since automated hacking programs can always by pass it?
[+] [-] satysin|10 years ago|reply
There are many such anti-patterns around like requiring "complex" passwords with upper, lower, special, etc. characters yet do not work with >16 characters. Something that pisses me off to no end is Microsoft not allowing spaces in their passwords for some unknown reason.
If it were up to me I would have one limit to passwords, length. A minimum of 12 characters. Sure you will get some moron using aaaaaaaaaaaa but they are the kind of people who will find a way to use an idiotic password no matter what.
The reality is passwords need to die. We should be encouraging pass-phrases.
[+] [-] rectang|10 years ago|reply
For a different approach, consider the distributed trust authorities of Apache Milagro (incubating):
http://milagro.incubator.apache.org/
[+] [-] quaunaut|10 years ago|reply
1. https://hashcat.net/oclhashcat/
[+] [-] pveierland|10 years ago|reply
They quickly replied that their entropy estimation was flawed in handling some characters and that they would fix this. They also said that copy/pasting was disallowed as this password should not be stored in any form. I sent them an email back arguing that this policy forces people to use weaker passwords, to which they replied that this would be taken to their product manager.
Now in 2016 they've updated their implementation which allows pasting passwords, making life easier.
[+] [-] kkirsche|10 years ago|reply
[+] [-] matthewmacleod|10 years ago|reply
What are the reasons that such inquiries often get stonewalled - is it simple organisational complexity, and the difficulty of actually contacting the right individual?
[+] [-] ikeboy|10 years ago|reply
(For the "type your new password twice to change it" fields there's somewhat of a justification: if someone mistypes their password then pastes it twice, they'll be locked out of their account, the point of the double field is to prevent typing errors, which means it should be typed twice.)
[+] [-] chrismorgan|10 years ago|reply
Getting email address wrong is far more important, but far fewer things do the same doubling up on that.
[+] [-] unknown|10 years ago|reply
[deleted]
[+] [-] strathmeyer|10 years ago|reply
[+] [-] po|10 years ago|reply
You could also alt-tab over to your IRC client (IRC because this was state of the art probably about when this practice started) and forget what is in your clipboard and paste+enter quickly.
I don't think this is a _good_ reason to do it, but that was why I thought it was done. I have no idea if that's the real reason it got started though.
[+] [-] erichurkman|10 years ago|reply
[+] [-] daenney|10 years ago|reply
Annoyingly so Apple has taken to this practice in certain OS password fields, like when you need to enter a password to decrypt a FileVault encrypted disk.
[+] [-] jamessb|10 years ago|reply
[1]: https://qsapp.com/
[+] [-] niteshade|10 years ago|reply
[+] [-] ivanhoe|10 years ago|reply
[+] [-] Strom|10 years ago|reply
[+] [-] joshmn|10 years ago|reply
[+] [-] nextweek2|10 years ago|reply
The main reason is the clipboard is plain text and shared with everything. I recently had it last week where my other half was using my laptop. The cat walked over the keyboard and she wondered where this person's name had come from. Turns out it was from me using the clipboard 5 days earlier.
It dawned on me then, the clipboard needs a time limit. It needs to clear after an hour of inactivity, it needs to clear on resume.
[+] [-] tony-allan|10 years ago|reply
I don't use software that disables paste.
[+] [-] Johnny555|10 years ago|reply
[+] [-] dannysu|10 years ago|reply
But I do agree it's rather annoying and not allowing paste is even worse.
I actually trust my copy-and-paste more than me not making a typo because I am human. By not allowing paste, websites are asking me to potentially make mistakes.
Perhaps a better solution is for the browser to have a button on <input type="email"> fields to allow me to select from a list of emails I have. The browser needs to protect this data from being website accessible until I give permission for privacy reasons, but that would have been a way better UX.
[+] [-] hjnilsson|10 years ago|reply
[+] [-] cube00|10 years ago|reply
[+] [-] paulddraper|10 years ago|reply
[+] [-] sheepleherd|10 years ago|reply
My biggest beef is the constant asking "do you want the browser to insecurely save this?" How did that become the default? No wonder people can't remember passwords if they never type them. I use many machines, and multiple browsers per machine and I don't synchronize them, so changing the remember passwords setting is such a chore I usually stick to clicking "remember never".
I don't think I can recall (dozens of years of computing) ever having a password hacked. Privilege escalation is the main threat.
[+] [-] 98Windows|10 years ago|reply
It adds to the image that passwords are something special and secret if you cannot use basic functionality.
[+] [-] tyingq|10 years ago|reply
[+] [-] teilo|10 years ago|reply
Windows will paste plain text unless the text field in question is explicitly identified as rich text.
[+] [-] minikites|10 years ago|reply
[+] [-] bblough|10 years ago|reply
Ironically, I switched to TurboTax, but didn't have the same issue because the login is done automatically via my bank login.
Does anyone know of a decent online tax app that doesn't disable the pasting of passwords?
[+] [-] taf2|10 years ago|reply
[+] [-] papageek|10 years ago|reply
[+] [-] IanCal|10 years ago|reply
[+] [-] livus|10 years ago|reply
[+] [-] fareesh|10 years ago|reply
[+] [-] regularfry|10 years ago|reply
[+] [-] Johnny555|10 years ago|reply
[+] [-] dkopi|10 years ago|reply
[+] [-] mschuster91|10 years ago|reply