Timeline for Why should I hash passwords?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 3, 2013 at 13:30 | history | edited | nerdybeardo | CC BY-SA 3.0 |
deleted 229 characters in body
|
| Jun 3, 2013 at 13:19 | history | edited | nerdybeardo | CC BY-SA 3.0 |
added 140 characters in body
|
| Jun 3, 2013 at 13:16 | comment | added | nerdybeardo | @Gilles Thanks for the clarification, I see your point and agree I'll make an edit. | |
| Jun 3, 2013 at 11:46 | comment | added | Gilles 'SO- stop being evil' | This is a good presentation, except for the first paragraph. Hashing passwords only defends against one thing: brute force attacks after the database is compromised. It's not two lines of defense, just the one. (Or you could call salting and slowness two lines of defense, but the important point is that the only use of hashing is to mitigate a database compromise, it does nothing about online brute-force attacks.) | |
| Jun 3, 2013 at 8:17 | history | edited | nerdybeardo | CC BY-SA 3.0 |
added 980 characters in body
|
| Jun 3, 2013 at 7:15 | history | migrated | from stackoverflow.com (revisions) | ||
| Jun 2, 2013 at 14:40 | history | answered | nerdybeardo | CC BY-SA 3.0 |