Timeline for How to evaluate the strength of a hashing algorithm?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 27, 2012 at 20:57 | answer | added | KeithS | timeline score: 1 | |
| Dec 27, 2012 at 19:16 | comment | added | us2012 | @Jeff: It's likely not because AnonEmployee thinks it should be kept secret, but certainly his boss will think so. Also, in the places I've worked at, posting full modules of the company's code online is likely to get you into a lot of trouble, no matter whether it's the hashing algorithm or the daily backup scripts... | |
| Dec 27, 2012 at 17:50 | answer | added | Thomas Pornin | timeline score: 5 | |
| Dec 27, 2012 at 14:41 | comment | added | Jeff | What 'obvious reasons' do you have for not posting the source? If you think it is because the algorithm needs to be kept a secret that is a clear indicator the algorithm is no good. | |
| Dec 27, 2012 at 14:18 | vote | accept | AnonEmployee | ||
| Dec 26, 2012 at 22:02 | history | tweeted | twitter.com/#!/StackSecurity/status/284056689710338050 | ||
| Dec 26, 2012 at 21:19 | answer | added | Lucas Kauffman | timeline score: 11 | |
| Dec 26, 2012 at 21:17 | answer | added | us2012 | timeline score: 3 | |
| Dec 26, 2012 at 21:04 | review | First posts | |||
| Dec 27, 2012 at 0:19 | |||||
| Dec 26, 2012 at 20:45 | history | asked | AnonEmployee | CC BY-SA 3.0 |