cryptography

From Kicksecure
< Dev
Jump to navigation Jump to search
Design Previous page: Project Policies Index page: Design Next page: Dev/Password Manager cryptography

todo

Documentation for this is incomplete. Contributions are happily considered! See this for potential alternatives.

https://crypto.stackexchange.com/questions/5118/is-aes-256-weaker-than-192-and-128-bit-versionsarchive.org iconarchive.today icon

https://www.schneier.com/blog/archives/2009/07/another_new_aes.htmlarchive.org iconarchive.today icon

Speed and its security impact Cryptographic performance problems have frequently caused users to reduce their cryptographic security levels or to turn off cryptography entirely.The security impact of a new cryptographic libraryarchive.org iconarchive.today icon by well-known, respected cryptographers [1]

The remaining risk is that users find NaCl too slow and turn it off, replacing it with low-security cryptographic software or no cryptography at all. NaCl avoids this type of disaster by providing exceptionally high speeds.

We have prioritized security over compatibility, and as a consequence have also prioritized speed over compatibility

Concretely, think about a demo showing that spending a billion dollars on quantum computation can break a thousand X25519 keys. Yikes! We should be aiming for much higher security than that! We don't even want a billion-dollar attack to be able to break one key! Users who care about the security of their data will be happy that we deployed post-quantum cryptography. But are the users going to say "Let's turn off X25519 and make each session a million dollars cheaper to attack"? I'm skeptical. I think users will need to see much cheaper attacks before agreeing that X25519 has negligible security value.https://blog.cr.yp.to/20240102-hybrid.htmlarchive.org iconarchive.today icon

Speed drives adoption, Daniel J. Bernstein (djb) probably understand this more than anyone else. And this is what led Adam Langley to decide to either stay on SHA-2 or move to BLAKE2. Is that a good advice? Should we all follow his steps?https://cryptologie.net/posts/maybe-you-shouldnt-skip-sha-3/archive.org iconarchive.today icon

The choice of key size is a tradeoff between the risk of key compromise and performance.http://csrc.nist.gov/publications/nistpubs/800-81r1/sp-800-81r1.pdfarchive.org iconarchive.today icon

* Are “special” primes dangerous?

These questions go far beyond 128 vs 256 vs 512 bits of security.

Footnotes

[edit]
    • Daniel J. Bernstein (Department of Computer Science, University of Illinois at Chicago, USA)
    • Tanja Lange (Department of Mathematics and Computer Science, Technische Universiteit Eindhoven, Netherlands)
    • Peter Schwabe (Research Center for Information Technology Innovation and Institute of Information Science, Academia Sinica, Taiwan)

Design Previous page: Project Policies Index page: Design Next page: Dev/Password Manager

Notification image

We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 13 year success story and maybe DONATE!