4 ms·
You edited your post after I replied. We're not writing our own cryptography, lol, we're using existing libraries based around OpenSSL using industry accepted
by marknadal 8y ago
You edited your post after I replied.
We're not writing our own cryptography, lol, we're using existing libraries based around OpenSSL using industry accepted and standardized algorithms and curves (ECDSA 256, AES 256, ECDH 256, PBKDF, etc.)
So yes, please email me the moment those get broken/cracked and we'll upgrade to whatever new standards are available.
- somenewacc 8y agoI hope you understand that you can use secure primitives (such as ECDSA and AES) to build insecure protocols.
- marknadal 8y agoAnd I hope you understand we've spent over a year with a large open source community collectively working on reviewing the implementation, discussing it with colleagues around the world from MIT and Navy personnel and more, working to make it secure, and even now still improving it. Do you have any vulnerability to report? Please send it in. Security is an always evolving process.