"That's the kind of [paid, personal] assurance you can count on [to make someone else money]." (TM)
> (384-bit prime) - Why not just use X448 since that's now an Internet Standard?
I believe they started working before X448 was standardized.
> It also uses Fortuna for IVs, etc. instead of directly /dev/urandom (or window.crypto in JS land). Userspace CSPRNGs are a devastatingly stupid idea.
IE doesn't have great support for window.crypto. If you're building an enterprise product, you probably care about this.
> FUD. Where you host the data shouldn't matter, because the server should never be given access to your plaintext.
I believe their point here was that most cloud services today DO have access to your plaintext. It's not FUD if it's true =).
I know I'm a bit biased, but these guys are pretty smart, and I'd trust them.
I know a lot of smart people who have made crypto mistakes.
If they want anyone to trust them, open source the app. Otherwise, GTFO.
(384-bit prime) - Why not just use X448 since that's now an Internet Standard?
AES-256-CCM is an interesting choice. At least it's an AEAD mode.
It also uses Fortuna for IVs, etc. instead of directly /dev/urandom (or window.crypto in JS land). Userspace CSPRNGs are a devastatingly stupid idea.
Where is the identity verification ("How do I know I'm speaking to the correct public key?")?
> Europeans: Did you know that when you use U.S. cloud services, your data is stored under US jurisdiction, and handled under under the Patriot Act? This means that a foreign government can inspect your or your client's data even without informing you.
FUD. Where you host the data shouldn't matter, because the server should never be given access to your plaintext.
My advice: Avoid like the plague.