Re: Was: Draft Blog Post on Cryptography API, Now: Potential API recommendation caveats

----- Original Message -----
> From: "David Rogers" <david.rogers@copperhorses.com>
> To: ddahl@mozilla.com, sleevi@google.com
> Cc: public-webcrypto@w3.org, hhalpin@w3.org
> Sent: Tuesday, October 9, 2012 12:25:23 PM
> Subject: Re: Was: Draft Blog Post on Cryptography API, Now: Potential API    recommendation caveats
> 
> Hi David,
> 
> I haven't been able to keep up with all the discussion, but is this a
> serious proposal to deploy an experimental crypto api in a
> production build? Apologies if I have missed something, but if
> people want to experiment that is fine, but don't do it in a shipped
> product, it doesn't make sense and will inevitably lead to security
> issues?

Yes, of course, people will still use this API unsafely, however, if the spec has security considerations that warn developers about using this API in content DOM as dangerous and browser vendors raise warnings upon use, and even (as horrible as this sounds) a geolocation-like prompt each time the API is first used per origin, developers and endusers will be warned. 

I think it should be up to the browser vendor exactly how this is handled - the API may even be preffed off in content DOM, only available to an "Open Webapp" or "SysApp".

Allowing it to be activated one way or another will still have value for developers working on experiments.

Cheers,

David

Received on Tuesday, 9 October 2012 19:19:00 UTC