Re:Challenge HN: Break my in-browser crypto for $1000
by chacham15 on Wednesday May 29, 2013 @02:59PM
(#5788320)
Hmmm, code-signed js would seem to fit the bill, no? I guess that fundamentally, it is still using the same CA structure that SSL is. This, however, has no solution even for compiled applications: if the servers private key is compromised then all bets are off.
Even if the user is somehow checking the exact JS bytes received (which is so pointless a stretch), what if the server is already compromised the first time the user gets there? Or they're on another computer?
And then, how do you deliver updates? If I compromise SSL or your server, I'll use that channel to tell people "we updated the code, it's good".
How is the user supposed to determine to trust the JS in the first place?
This literally boils down to strength of SSL.
Create something in JS that doesn't rely on SSL, and then you'll have something to show off.