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/
@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 -
@bascule@BrendanEich@ashk4n ever put a passphrase on a production SSL cert? :) -
@dakami@BrendanEich@ashk4n no, but TLS aside we keep our encryption keys for sensitive data airgapped: http://www.slideshare.net/diogomonica/bletchley … - 15 more replies
New conversation -
-
-
@bascule@BrendanEich@ashk4n@dakami I only know that Windows Update signs code because Flame find a way around it. -
@dan_crowley@BrendanEich@ashk4n@dakami yeah, through a hash collision, requiring a state-level attacker -
@bascule@BrendanEich@ashk4n@dakami Yes, it was quite a piece of work. Just noting that crypto is never in a vacuum. -
@dan_crowley@bascule@BrendanEich@ashk4n that's the point, the state level attacker hewed precisely to Stevens/Sotirov.
End of conversation
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.