Secure origin requirement in Chrome/WebCrypto

During my work with a WebCrypto-enabled application I found that
Firefox "Nightly" and Chrome "Canary" have different behavior.

Chrome apparently requires HTTPS (presumably also with a "genuine"
certificate) for executing some (?) methods like import of keys.

I perfectly well understand the motives but it makes *development* harder.
IMO, it would be better to making this requirement a recommendation.

WebCrypto won't anyway be useful for people who lack insight in applied
cryptography, secure protocols and server hardening but that's entirely OK :-)

Cheers,
Anders

Received on Thursday, 25 September 2014 06:26:48 UTC