Why browser-based crypto sucks: MEGApwn bookmarklet shows just how easy it is to get access to your MEGA private key http://nzkoz.github.io/MegaPWN/
@BrendanEich @dakami @ashk4n at any time they could push code that instructs your browser to hand over your "secret master key" to them
-
-
@bascule@BrendanEich@ashk4n see also Windows Update -
@dakami@BrendanEich@ashk4n at least Windows Update signs code (I assume?) A web browser takes whatever the server presents at face value -
@bascule@BrendanEich@ashk4n SSL signs code (and everything else) -
@dakami@BrendanEich@ashk4n please see page 2, under "Main contributions": https://isis.poly.edu/~jcappos/papers/samuel_tuf_ccs_2010.pdf … -
@bascule@BrendanEich@ashk4n like keying isn't hard enough, that we need more keys. I swear, people need to do tours of duty in ops -
@dakami@BrendanEich@ashk4n see what happened to RubyGems with the YAML vulnerability, or more recently with TorBrowser -
@bascule@BrendanEich@ashk4n cryptographers have a habit of treating ops like a massive externality -
@dakami@BrendanEich@ashk4n I work in ops, FYI - 17 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.