W3C home > Mailing lists > Public > public-webcrypto@w3.org > April 2014

[Bug 25345] Set window.crypto and all properties of window.crypto writable to false

From: <bugzilla@jessica.w3.org>
Date: Tue, 15 Apr 2014 20:06:49 +0000
To: public-webcrypto@w3.org
Message-ID: <bug-25345-7213-qDfYoyq0AH@http.www.w3.org/Bugs/Public/>

Andreas <kuehne@trustable.de> changed:

           What    |Removed                     |Added
                 CC|                            |kuehne@trustable.de

--- Comment #9 from Andreas <kuehne@trustable.de> ---
Yes, I can understand the arguments for just doing nothing ... this little
topic wouldn't save the crypto world.

On the other hand I'm pestered by many mad restrictions when trying to use a
Java applet as a surrogate for browser crypto. Many things seem strange or
useless to me. But in the applet domain the mantra is 'every little helps!' ...
OK then ... Now I'm a bit astound that just few processor cycles beyond the
applet the approach is so completely different! 

Is this just a clash of cultures or do I just don't get the full picture?

You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 15 April 2014 20:06:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:02:42 UTC