3 ms·
Author here: if people aren't familiar with webcrypto (https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API https://developer.mozilla.org/en-US/docs/
by nailer 10y ago
Author here: if people aren't familiar with webcrypto (https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_...) it's a way to do real crypto, using the OS and openssl / boringssl (Google's openssl fork). I.e., it's not 'JavaScript crypto', but actually has proper randomness, hence properly unguessable keys. When we make keypairs with webcrypto, the private key never leaves the browser, so CertSimple doesn't know it.
That said, if a user prefers to make keys on their own machine we create a custom bash / powershell script to create the necessary CSR and private key in a single paste - no clicking, no Q and A, and without installing anything.
- tptacek 10y agoWebCrypto is browser Javascript crypto. You cannot rely on it to allow browsers to keep secrets from servers: the server has a variety of different straightforward ways to compromise cryptosystems it feeds to browsers. Randomness is far from the most important problem with browser Javascript crypto; critics of browser crypto generally assumed that browser Javascript would get secure randomness at some point. The most important problem with this scheme is that there's no way to provide assurance that the browser JS runtime is what the user of an application expects it to be. WebCrypto was chartered as a way to recreate the DRM schemes that Flash video plugins relied on, without needing plugins. You can read the working group notes to see that. It was never intended as, and cannot function as, a way of creating "server-proof" crypto apps.
- nailer 10y ago> The most important problem with this scheme is that there's no way to provide assurance that the browser JS runtime is what the user of an application expects it to be. That's correct. We only use the native runtime (ie, no shims) but obviously users have to trust that that's the case unless they want to inspect the code. If there's no working window.crypto (or for certain blacklisted platforms with partial implementations) we go straight to out-of-browser keygen. Furthermore, the user has to trust that we're not sending the private key back to us by some channel: they could do this fairly easily by inspecting the code but if they're uncomfortable it's easier to click the 'make keys on my server' option.
- koolba 10y agoThere's a typo on your FAQ: https://certsimple.com/help/web-server-support https://certsimple.com/help/web-server-support The last line just says, "We'll handle". Looks like it's truncated.
- nailer 10y agoThanks for the heads up Koolba. Fixed!