Timeline for Why not allow spaces in a password?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2018 at 14:53 | comment | added | Mac | It's 2018. We have Unicode 10.0 containing 1,114,112 enumerated graphemes. Of those, 136,690 are assigned and named. That's 17.061 bits of entropy per symbol (that could be used). It's past time the industry kept pace with technology and stopped regurgitating policies of the last 3 decades. There may well have been very practical & technical reasons to prohibit UTF-8 codepoint 32, but they don't exist now. To make a passphrase, users should be free to use any Unicode codepoint; resulting in a salted, hashed, stretched (or rotated) encryption key. | |
| May 5, 2018 at 19:03 | comment | added | user46818 | A space character doesn't represent "null space". Outside of some Unicode representations, it's just a string of eight bits, as letters and numbers are. Also, a zero isn't an absence of numerical value; it's a placeholder that has meaning. If you doubt this, binary-replace all '10000000'x with '00000001'x in one of your executables and see what happens. :) | |
| Mar 27, 2018 at 23:33 | review | Late answers | |||
| Mar 27, 2018 at 23:45 | |||||
| Mar 27, 2018 at 23:18 | review | First posts | |||
| Mar 28, 2018 at 3:32 | |||||
| Mar 27, 2018 at 23:16 | history | answered | Steve Warnek | CC BY-SA 3.0 |