On Sep 25, 2014, at 4:32 AM, Ben Laurie <[email protected]> wrote: >> 1. Gossip could be blocked. > > Blocking our proposed mechanism == blocking all TLS. So, it could be, > but it would be kinda obvious...
Where do you specify that blocking gossip = blocking TLS? And where do you specify the details of how gossip works? Still isn't in RFC 6962... >> 2. If Gossip isn't blocked, and you're able to prove failure... so what? >> What then? The RFC is rather silent on this. Any support with this question? >> The blockchain, on the other hand, doesn't have problem #2. >> >> Even if MITM suddenly starts blocking all new blocks and only showing blocks >> it creates, the node has a giant store of accurate data that the MITM cannot >> modify. Not so with CT. > > Why not? Because the contents of the entries in the blockchain belong to their respective owners. > If clients want to download the whole log, they can. Ben, according to your documentation, clients do not download whole logs, Monitors do. Monitors are not web browsers. Now, you're welcome to come back at me and say that Google Chrome is going to start downloading "All The Logs!", but something tells me you're not going to do that. Kind regards, Greg -- Please do not email me anything that you are not comfortable also sharing with the NSA.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Messaging mailing list [email protected] https://moderncrypto.org/mailman/listinfo/messaging
