Timeline for Can I use my own implementation of a widely used, supposedly secure cryptographic algorithm for securing data at rest?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 19, 2020 at 12:31 | vote | accept | CommunityBot | ||
| Sep 19, 2020 at 12:31 | |||||
| Jul 10, 2020 at 5:22 | comment | added | Gordon Davisson | @nobody Just because your implementation matches known tests doesn't mean it doesn't have terrible problems. For example, if you used GCM mode but you goofed up the IV randomization and used some duplicates, or you used ECB mode, or you used the encryption key for something else that allows it to be inferred, or ... any of a zillion other mistakes. | |
| Jul 8, 2020 at 9:14 | history | migrated | from security.stackexchange.com (revisions) | ||
| Jun 30, 2020 at 9:20 | comment | added | user80567 | So you mean if my implementation matches the known answer tests and other implementations, it should provide as much security for data at rest as the other implementations, but its still a bad idea? | |
| Jun 29, 2020 at 19:38 | history | answered | dandavis | CC BY-SA 4.0 |