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 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 … -
@bascule@dakami@BrendanEich@ashk4n Yikes, those are some real disadvantages. Especially the cross-DC problem. -
@grittygrease@dakami@BrendanEich@ashk4n cross-DC problem is solvable, and HSMs are a PITA but certainly help pass PCI audits ;) -
@bascule@dakami@BrendanEich@ashk4n But why a centralized HSM service instead of a distributed service based on low cost TPMs? -
@grittygrease Bletchley is decentralized with no single point of failure. See the note at the end of slide #33 /cc@dakami - 11 more replies
New conversation -
-
-
@bascule@BrendanEich@ashk4n the disasters that befall offline keying systems blow online keying out of the water - 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.