My guess is it uses Chrome&#x27;s Native Client [1] for crypto. It&#x27;s understandable why they might want to do this at this point in time, because the only other way to use native code for crypto in the browser is through the the Web Crypto API [2], which is still very young and implementations aren&#x27;t very consistent across browsers yet anyways.<p>[1] <a href="https:&#x2F;&#x2F;developer.chrome.com&#x2F;native-client" rel="nofollow">https:&#x2F;&#x2F;developer.chrome.com&#x2F;native-client</a><p>[2] <a href="http:&#x2F;&#x2F;www.w3.org&#x2F;TR&#x2F;WebCryptoAPI&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.w3.org&#x2F;TR&#x2F;WebCryptoAPI&#x2F;</a>