Timeline for Reason for not implementing own algorithms/implementations [duplicate]
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 2, 2018 at 9:08 | vote | accept | user4139197 | ||
| Jul 2, 2018 at 8:23 | comment | added | schroeder♦ | Cryptographic development in a programming language != software development. You cannot use the learning methods in the latter as a learning path in the former. | |
| Jul 2, 2018 at 8:21 | history | closed |
Steffen Ullrich Xander user165253 schroeder♦ |
Duplicate of Why shouldn't we roll our own?, What does "don't roll your own security" mean? | |
| Jul 2, 2018 at 8:19 | history | edited | schroeder♦ | CC BY-SA 4.0 |
edited tags
|
| Jul 2, 2018 at 8:19 | comment | added | schroeder♦ | @user4139197 "Security" algorithm or "Cryptographic" algorithm? There is a massive difference between the two. | |
| Jun 30, 2018 at 20:20 | comment | added | forest | @user4139197 Only 3 years? You're looking at 10 or 20 years if you actually want to develop and implement your own algorithms. I'm not exaggerating. You can learn some basics of cryptography by reading various books or taking classes, but those will absolutely not teach you enough to create your own algorithms. You can learn what block modes are safe and in what circumstances (where to use GCM, CBC, etc), or you can learn the different types of ciphers (SPN, ARX, Feistel, Lai-Massey, etc), but you still won't be able to create your own. Also, check out Cryptography. | |
| Jun 30, 2018 at 20:19 | comment | added | user4139197 | @forest Generally a good idea yes but what about people that want to get into cryptography and want to understand the basic concepts before making it a 3 year commitment | |
| Jun 30, 2018 at 20:17 | comment | added | forest | How can one be able to learn more about security if not implementing such things himself and learning from his faults Get a PhD in cryptography first. Read and understand all the seminal works of famous cryptographers like McElice, Shamir, Bernstein, Preneel, Diffie, etc. Otherwise you won't even know what faults you have in order to learn from them. It's not like software development where "it works" means you did it more or less right. | |
| Jun 30, 2018 at 14:09 | review | Close votes | |||
| Jul 2, 2018 at 8:23 | |||||
| Jun 30, 2018 at 14:03 | answer | added | Pacopaco | timeline score: 0 | |
| Jun 30, 2018 at 13:57 | answer | added | Chris Tsiakoulas | timeline score: 2 | |
| Jun 30, 2018 at 13:50 | comment | added | Steffen Ullrich | It is nothing really wrong to play around with own algorithms in order to learn. But usually the OP asking these question to not state explicitly that this is just for playing around and that they would never would use it in production anyway - which then results in the reaction you describe (don't roll your own). " How can one be able to learn more about security if not implementing such things himself and learning from his faults ?!" - First learn the design decisions behind existing systems and why they work like this and then maybe try own ideas in order to not fail immediately. | |
| Jun 30, 2018 at 13:34 | review | First posts | |||
| Jun 30, 2018 at 15:55 | |||||
| Jun 30, 2018 at 13:33 | history | asked | user4139197 | CC BY-SA 4.0 |