<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;">I echo Trevor's comments, it's important to directly link PKI to e2e (and to mention how this conversation would be different from the ones that have already taken place multiple times on this list on the same topic).<div><br></div><div>At the same time, it should be acknowledged that PKI itself does have direct relevancy to end-to-end secure messaging in terms of ease-of-use, as well as the inherent security improvements that come from said ease-of-use improvements.</div><div><br></div><div>I am referring to:</div><div><br></div><div>1. Manual fingerprints verification (which users must learn to do properly)</div><div>2. Managing keys and updating them ("TheRightKey" problem)</div><div><br></div><div>That is why I've been pushing a "One Pin To Rule Them All" approach with DNSChain [1], where fingerprint verification only needs to happen one time, after which all end-to-end messaging apps benefit in that they no longer require fingerprint verification.</div><div><br></div><div>At the same time a rather good competing proposal to DNSChain has surfaced that preserves many of the same properties, but at the expense of being far more difficult and challenging to implement, and that is full-security thin clients for blockchains like Namecoin and others.</div><div><br></div><div>I think both approaches are good, and ultimately I would even favor full-security thin clients, especially to blockchains with stronger/better consensus mechanisms than Namecoin.</div><div><br></div><div>Until full-security thin-clients ("SPV+", "Ultimate blockchain compression", etc.) come about, DNSChain provides a workable alternative, IMO.</div><div><br></div><div>Cheers,</div><div>Greg Slepak</div><div><br></div><div>[1] <a href="https://github.com/okTurtles/dnschain/blob/master/docs/What-is-it.md#MITMProof">https://github.com/okTurtles/dnschain/blob/master/docs/What-is-it.md#MITMProof</a></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 Jan 23, 2015, at 3:05 PM, Trevor Perrin <<a href="mailto:trevp@trevp.net">trevp@trevp.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi,<br><br>Are we just discussing website login and Web PKI here?<br><br>If there's no direct connection to end-to-end secure messaging, could<br>people discuss this elsewhere?<br><br>Trevor<br><br><br>On Fri, Jan 23, 2015 at 1:01 PM, Tony Arcieri <<a href="mailto:bascule@gmail.com">bascule@gmail.com</a>> wrote:<br><blockquote type="cite">On Fri, Jan 23, 2015 at 1:57 AM, U.Mutlu <<a href="mailto:for-gmane@mutluit.com">for-gmane@mutluit.com</a>> wrote:<br><blockquote type="cite"><br>Back to the roots: hashed pw over MITM-safe sessions (SRP, SPEKE etc, ie.<br>PAKE).<br></blockquote><br><br>These aren't MITM safe. They're TOFU. They have no way to authenticate the<br>server.<br><br>When you enroll a PAKE account, if you're talking to a MITM server, you're<br>toast. The MITM can then enroll with the real service on your behalf and<br>transparently proxy everything through, except the MITM will have the real<br>credentials, and your credentials will only work with the MITM.<br><br>Also: passwords suck and need to go away.<br><br>--<br>Tony Arcieri<br><br>_______________________________________________<br>Messaging mailing list<br><a href="mailto:Messaging@moderncrypto.org">Messaging@moderncrypto.org</a><br>https://moderncrypto.org/mailman/listinfo/messaging<br><br></blockquote>_______________________________________________<br>Messaging mailing list<br><a href="mailto:Messaging@moderncrypto.org">Messaging@moderncrypto.org</a><br>https://moderncrypto.org/mailman/listinfo/messaging<br></blockquote></div><br></div></body></html>