News for hackers. Stuff that matters.
Re:Cryptography in the Browser by tinco on Tuesday October 29, 2013 @08:45PM (#6638660)
Please note the implications of this. The signed javascript would have to be hosted on a separate third party website, and it would have to be the _only_ script content of the website.

Since code can be executed by almost every resource on a webpage, basically the entire would have to be stored on that separate third party website, the html, the css, maybe throw in the images too given their history of weird exploits.

Not saying that's a very crazy idea, but I'm saying it's way beyond the scope of these opal guys, and probably not what most people 'working out' browser crypto are after.

Re:Cryptography in the Browser by jerrya on Tuesday October 29, 2013 @09:01PM (#6638723)
And yet, jsquery works that way, doesn't it? Everyone pulls jsquery in from basically one site...

Does the entire website have to be on that separate third party location, or just a self-booting kernel of crypto to enable a signed website to be downloaded from the desired source?

Re:Cryptography in the Browser by elithrar on Tuesday October 29, 2013 @10:43PM (#6639114)
> And yet, jsquery works that way, doesn't it? Everyone pulls jsquery in from basically one site...

Not everyone (not even close). Many do, but if I'm running a site over SSL I'm going to be hosting my own copy of the jQuery libs.