Timeline for Securely handling a password protected application
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 1, 2016 at 3:57 | answer | added | Roland Illig | timeline score: 0 | |
| Jan 5, 2016 at 6:37 | history | edited | 200_success |
edited tags
|
|
| Jan 4, 2016 at 23:47 | history | edited | Jamal | CC BY-SA 3.0 |
deleted 143 characters in body; edited title
|
| Mar 1, 2011 at 18:00 | vote | accept | JakeParis | ||
| Feb 22, 2011 at 22:02 | answer | added | Mark Loeser | timeline score: 5 | |
| Feb 22, 2011 at 18:31 | answer | added | davidhaskins | timeline score: 6 | |
| Feb 21, 2011 at 12:49 | answer | added | David Gillen | timeline score: 1 | |
| Feb 17, 2011 at 16:26 | comment | added | andrew-e | crypt() might fall back to MD5 or something else if there is no support for blowfish, or if the salt isn't right. us.php.net/crypt To be sure, you could try phpass with PHP 5.3.0+ or the Suhosin patch: openwall.com/phpass | |
| Feb 17, 2011 at 15:02 | comment | added | JakeParis |
Ah, interesting. So can I just sub out my hash('sha256',$password) function with crypt($password,'$2a$12$1234567890123456789012$') (obviously with a different salt string).
|
|
| Feb 17, 2011 at 14:56 | history | edited | JakeParis | CC BY-SA 2.5 |
added mysql_real_escape_string
|
| Feb 16, 2011 at 19:35 | comment | added | andrew-e | This should be relevant: How To Safely Store A Password (bcrypt) | |
| Feb 16, 2011 at 17:00 | answer | added | 65Fbef05 | timeline score: 1 | |
| Feb 16, 2011 at 14:52 | history | tweeted | twitter.com/#!/StackCodeReview/status/37887076552802304 | ||
| Feb 16, 2011 at 14:35 | history | asked | JakeParis | CC BY-SA 2.5 |