On Thu, Sep 11, 2014 at 6:56 PM, Richard Barnes <rbar...@mozilla.com> wrote: > No, WebCrypto on an http:// origin is not a replacement for TLS.
Addressing confusion on this point seems to be the main driver of Chrome's restriction of Web Crypto to authenticated origins. Is there any way to quantify in advance how damaging it would be to fail to actively undermine this confusion? (I.e. how broadly will the enablement of Web Crypto on http origins cause the non-adoption of TLS with proper certs?) BTW, regarding https://twitter.com/sleevi_/status/509939303045005313 , when running with e10s, is the NSS instance backing Web Crypto in the content process and separate from the NSS instance doing TLS in the chrome process? -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
