Timeline for Golang crypto library: security
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 29, 2018 at 2:04 | answer | added | Maarten Bodewes | timeline score: 6 | |
| Mar 1, 2017 at 8:05 | history | tweeted | twitter.com/StackCodeReview/status/836849923681312768 | ||
| Feb 27, 2017 at 16:31 | comment | added | CCooper | Thanks for the input. The core golang stdlib implements the real meat of the crypto, but it's still hard for people to use and understand without a lot of research. The only other library I'm aware of that does anything similar is github.com/gtank/cryptopasta, but (maybe rightly) does not provide examples for anything other than gcm. If there are other libraries out there I'm happy to defer to those as well. Additionally, mine implements a standard interface, so at some point, if GCM is broken and a new standard is introduced, it would be trivial to reuse existing code. | |
| Feb 27, 2017 at 16:22 | comment | added | Thomas Ward | I'm confused, you say you aren't rolling your own crypto, but you're creating your own crypto library. Correct me if I'm wrong, but aren't there other crypto libs already out there that have had a lot more vetting from a security perspective? | |
| Feb 27, 2017 at 15:59 | review | First posts | |||
| Feb 27, 2017 at 16:02 | |||||
| Feb 27, 2017 at 15:56 | history | asked | CCooper | CC BY-SA 3.0 |