Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro...
by xenadu02 on Friday January 15, 2016 @12:16PM
(#10910631)
I think you underestimate inertia. Once encrypting JS is just a checkbox in your IDE, management and lazy developers will just check it.
[ Parent
| on HN ]
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro...
by epistasis on Friday January 15, 2016 @12:44PM
(#10910788)
Aha, so encrypted javascript is something new that I've not seen mentioned in any of these discussions!
However, does EME allow encryption of javascript? I thought it was just for playback elements in <video> and <audio>? Searching a bit, I can't find evidence that executable javascript could be encrypted.
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro...
by JoshTriplett on Friday January 15, 2016 @01:42PM
(#10911191)
I've seen proposals to allow EME to control access to any browser resource: images, fonts, scripts, even HTML itself. The proposals I've seen look a lot like Service Worker, but with an opaque obfuscated container running a blob.
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro...
by pjc50 on Friday January 15, 2016 @02:22PM
(#10911454)
Good news for unblockable adverts and ad-delivered malware! Running code that can't be inspected or blocked is really not a good idea.
Re:You Can't Destroy the Village to Save It: W3C vs. DRM, Ro...
by chris_wot on Friday January 15, 2016 @04:46PM
(#10912377)
That confirms what I wrote in bug 923950.