Timeline for How to store salt?
Current License: CC BY-SA 4.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Oct 30, 2018 at 13:27 | history | edited | Jacco | CC BY-SA 4.0 |
deleted 3 characters in body
|
Jan 9, 2018 at 21:19 | comment | added | Kellen Stuart | @Polynomial where do you store the salt then? It seems if the attacker finds the salt they can break into the database? | |
Sep 14, 2017 at 19:02 | history | edited | Jacco | CC BY-SA 3.0 |
added 7 characters in body
|
Jun 28, 2017 at 19:09 | comment | added | Zack | Alongside the hashed, salted, password. | |
May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
Mar 17, 2017 at 13:14 | history | edited | CommunityBot |
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
|
|
Jul 31, 2012 at 2:32 | vote | accept | George | ||
Jul 31, 2012 at 2:32 | |||||
Jul 20, 2012 at 13:41 | comment | added | Piskvor left the building | @Terry Chia: Prepending is more common. | |
Jul 20, 2012 at 13:17 | comment | added | user10211 | @Polynomial You made a very good point. Perhaps you would like to write an answer that covers what you have stated? I'd certainly upvote it, and it is much easier to read that way. | |
Jul 20, 2012 at 7:51 | comment | added | Polynomial | Keep in mind that if the salt is leaked (e.g. through a flaw in your code) the attacker can build a rainbow table for that salt ahead of time. This makes it difficult for you to take preventative measures if someone steals your hashes later, because they can immediately crack the password (they already have the rainbow table!) and access the account. | |
Jul 20, 2012 at 7:37 | history | answered | Jacco | CC BY-SA 3.0 |