title: WebcryptoAPI - secure or not?
body: <p>This is about the new W3 WebcryptoAPI draft standard - <a href="http://www.w3.org/2012/webcrypto/WebCryptoAPI/" rel="nofollow">http://www.w3.org/2012/webcrypto/WebCryptoAPI/</a></p>
  
  <p>Here is a post by one of it's authors</p>
  
  <p><a href="https://plus.google.com/u/0/105761279104103278252/posts/CSwVZ1RUijo" rel="nofollow">https://plus.google.com/u/0/105761279104103278252/posts/CSwVZ1RUijo</a></p>
  
  <p>It says its in part trying to change the "Javascript Cryptography Considered Hamrful" problem. However if you look at the "Javascript Cryptography Considered Hamrful" article -  <a href="http://www.matasano.com/articles/javascript-cryptography/" rel="nofollow">http://www.matasano.com/articles/javascript-cryptography/</a> - it seems as if most of the problems still remain unsolved. The only problem solved is that you won't have hand coded cryptographic functions in javascript - these will be provided by the browser. However, the remaining problems still remain.</p>
  
  <p>Your thoughts?</p>