News for hackers. Stuff that matters.
Re:Could keybase.io do for crypto what GitHub did for Git? by malgorithms on Tuesday March 25, 2014 @09:03AM (#7465550)
The client verifies the key by checking that the signed tweet, gists, etc., all exist and were signed by the private key that matches that public key. So to get the server to successfully lie, one would need to coordinate lies from twitter, github, etc., all at the same time.
Re:Could keybase.io do for crypto what GitHub did for Git? by schrodinger on Tuesday March 25, 2014 @09:44AM (#7465756)
And it would be really hard to get all those services to lie without the recipient being able to tell. They could see that their tweet contains a different fingerprint than they expected, unless you got all those services to lie only to the sender, not the recipient. Which is very hard to do without getting caught.
Re:Could keybase.io do for crypto what GitHub did for Git? by xgbi on Tuesday March 25, 2014 @10:34AM (#7466071)
DNS highjack and boom?