Timeline for Optimal Key Length for Encryption Protocols Balancing Security and Performance
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 27 at 10:33 | comment | added | Maarten Bodewes♦ | In general we focus on getting high quality random values out of an entropy source. There are good ways of doing that, specifically DRBG's have been defined to do this (KBKDF's with extraction propertjes may be applicable too, depending on context). As for "could enhance security in environments where threats are increasingly sophisticated." Sure, but 256 bit AES, SHAKE-256 and SHA-512 have withstood quite a bit of security and would be secure against a quantum computer / Grover even if one could be constructed. | |
| Nov 27 at 10:28 | history | edited | Maarten Bodewes♦ | CC BY-SA 4.0 |
added 90 characters in body
|
| Nov 26 at 23:22 | comment | added | Jon | Some of the stuff is super applicable and plug and play with modern standards too. Should I focus on just doing that instead of an entirely new system all together? I mean I really like the system we developed. | |
| Nov 26 at 23:17 | comment | added | Jon | In our work with EchoKey, we’ve experimented with dynamically evolving keys, and in its current configuration, the system generates keys that are significantly longer than standard. The reasoning here was to explore how expanded key space, combined with evolving entropy and layered transformations, could enhance security in environments where threats are increasingly sophisticated. The larger key length is a byproduct of focusing on high entropy and randomness across multiple dimensions. The system is designed to handle these lengths efficiently without prohibitive performance trade-offs | |
| Nov 26 at 16:59 | comment | added | poncho | "NIST usually also identifies 192 as an in-between security level, but that generally receives less attention." - depends on the system. No one uses AES-192, however for ML-KEM, people appear to be focusing on ML-KEM-768 (192 bit security strength classically) | |
| Nov 26 at 13:01 | history | answered | Maarten Bodewes♦ | CC BY-SA 4.0 |