Timeline for Why do some websites and programs restrict password characteristics?
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 6, 2016 at 8:40 | history | edited | S.L. Barth is on codidact.com | CC BY-SA 3.0 |
edited body
|
| Sep 12, 2013 at 18:47 | history | edited | Thomas Pornin |
edited tags
|
|
| Jan 14, 2011 at 1:34 | history | edited | Scott Pack |
edited tags
|
|
| Jan 12, 2011 at 4:55 | history | tweeted | twitter.com/#!/StackSecurity/status/25053240584310784 | ||
| Jan 10, 2011 at 22:27 | vote | accept | TheLQ | ||
| Jan 10, 2011 at 14:28 | answer | added | Thomas Pornin | timeline score: 11 | |
| Jan 10, 2011 at 4:19 | answer | added | D.W. | timeline score: 11 | |
| Jan 10, 2011 at 2:34 | comment | added | TheLQ | @Bill I was thinking more of securing the password when https isn't available, then adding your salt on the server. But thats off topic. | |
| Jan 10, 2011 at 1:49 | comment | added | Bill Weiss | You don't do the initial hash on the client side. If you did, it would mean that a bad client could just use the hash as the password, thus reducing the password strength down to whatever your hash size is :) | |
| Jan 10, 2011 at 1:25 | comment | added | ygjb | Since my first question missed the mark, I provide a separate answer. The primary reason is that limits are required. Although the concern regarding the storage space and the marginal load of calculating the hash of an arbitrary length chunk of data is accurate, there are some issues. | |
| Jan 10, 2011 at 1:20 | answer | added | Jakob Borg | timeline score: 21 | |
| Jan 10, 2011 at 1:06 | answer | added | Rory Alsop♦ | timeline score: 3 | |
| Jan 10, 2011 at 1:05 | answer | added | ygjb | timeline score: 1 | |
| Jan 9, 2011 at 21:31 | history | asked | TheLQ | CC BY-SA 2.5 |