<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Dear Ben,<div><br></div><div>In respecting Trevor's concern that CT is off topic for this list, I decided to reply to this email of yours over on [randombit] here:</div><div><br></div><div><a href="http://lists.randombit.net/pipermail/cryptography/2014-September/006800.html">http://lists.randombit.net/pipermail/cryptography/2014-September/006800.html</a></div><div><br></div><div>Feel free to send replies over there (or on [trans] if you'd like). On second thought, I probably should have sent it to [trans]... sorry, my mistake.</div><div><br></div><div>Kind regards,</div><div>Greg Slepak</div><div><div>
<br class="Apple-interchange-newline"><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none;">--</span><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none;">Please do not email me anything that you are not comfortable also sharing</span><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none;"> with the NSA.</span>
</div>
<br><div><div>On Sep 27, 2014, at 4:38 AM, Ben Laurie <<a href="mailto:ben@links.org">ben@links.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On 27 September 2014 01:16, Tao Effect <<a href="mailto:contact@taoeffect.com">contact@taoeffect.com</a>> wrote:<br><blockquote type="cite">On Sep 25, 2014, at 4:32 AM, Ben Laurie <<a href="mailto:ben@links.org">ben@links.org</a>> wrote:<br><br><br>1. Gossip could be blocked.<br><br><br>Blocking our proposed mechanism == blocking all TLS. So, it could be,<br>but it would be kinda obvious...<br><br><br>Where do you specify that blocking gossip = blocking TLS?<br><br>And where do you specify the details of how gossip works? Still isn't in RFC<br>6962...<br></blockquote><br>It will never be in RFC 6962 (RFCs can't be substantially changed<br>after publication).<br><br>Since you've read the article<br>(<a href="http://queue.acm.org/detail.cfm?id=2668154">http://queue.acm.org/detail.cfm?id=2668154</a>), you already know I've<br>discussed gossip in it.<br><br><blockquote type="cite">2. If Gossip isn't blocked, and you're able to prove failure... so what?<br>What then? The RFC is rather silent on this.<br><br>Any support with this question?<br><br>The blockchain, on the other hand, doesn't have problem #2.<br><br>Even if MITM suddenly starts blocking all new blocks and only showing blocks<br>it creates, the node has a giant store of accurate data that the MITM cannot<br>modify. Not so with CT.<br><br><br>Why not?<br><br><br>Because the contents of the entries in the blockchain belong to their<br>respective owners.<br><br>If clients want to download the whole log, they can.<br><br><br>Ben, according to your documentation, clients do not download whole logs,<br>Monitors do. Monitors are not web browsers.<br></blockquote><br>a) "Monitor" is a role - anything can be in that role.<br><br>b) If there's an advantage to downloading the whole log, a client is<br>free to do so. You claim that there's an advantage to having history<br>up to some point - I am just observing that CT allows the same thing,<br>at similar cost.<br><br><blockquote type="cite">Now, you're welcome to come back at me and say that Google Chrome is going<br>to start downloading "All The Logs!", but something tells me you're not<br>going to do that.<br></blockquote><br>Yeah, and we're not going to download "all the blockchain" either. But<br>if we were prepared to do that, then we could also download the CT<br>log.<br><br><blockquote type="cite"><br>Kind regards,<br>Greg<br><br>--<br>Please do not email me anything that you are not comfortable also sharing<br>with the NSA.</blockquote></div></blockquote></div><br></div></body></html>