Timeline for Is there a better way to take advantage of current 'approved', 'proven', and memory/cpu-expensive algorithms while using salts and peppers?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 9:49 | history | edited | CommunityBot |
Commonmark migration
|
|
| Mar 17, 2017 at 13:21 | history | edited | CommunityBot |
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
|
|
| Nov 2, 2012 at 20:36 | comment | added | clay richardson | @ScottPack - I'm actually asking five questions in one regarding this authentication and password/email storage implementation I've come up with. The questions are listed at the top, and the implementation follows down to the bottom. | |
| Nov 2, 2012 at 20:26 | comment | added | clay richardson | I already know that rolling your own crypto is a bad idea. That's why I'm using standard cryptographic primitives, and not coding up my own. @Jacco - Thanks for the tip on combining salt and pepper for bcrypt. | |
| Nov 2, 2012 at 7:36 | comment | added | Rory Alsop♦ | As @Jacco, and no doubt others will tell you in great detail - do not roll your own crypto! - See meta.security.stackexchange.com/a/915/485 | |
| Nov 2, 2012 at 7:18 | answer | added | Jacco | timeline score: 5 | |
| Nov 2, 2012 at 6:54 | comment | added | Jacco | read: security.stackexchange.com/questions/21263/… | |
| Nov 2, 2012 at 3:36 | comment | added | Scott Pack | Welcome to Security.SE! Reading through this I'm having trouble figuring out what your actual question is. Would you care to clarify it, please? | |
| Nov 2, 2012 at 1:45 | review | First posts | |||
| Nov 2, 2012 at 3:36 | |||||
| Nov 2, 2012 at 1:29 | history | asked | clay richardson | CC BY-SA 3.0 |