Javascript Crypto. Ugly duckling with good reason?
summary
Javascript crypto is risky because code ships from servers so MITM or a rogue backend can swap it, the language lacks native 32‑bit and big integer support and browsers historically lack a CSPRNG so Math.random is useless for keys, but asm.js makes integer ops fast and the W3C Web Cryptography API adds big integer and secure random support, fully homomorphic encryption is promising but impractical today, and a higher level library like the Crypt ruby project is built to wrap low level APIs and simplify secure usage.
AI-written summary · about
