<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I am not a big fan of this idea. We want to see 4096 bit crypto, so we need to be working towards a migration of both servers and clients to support that. Super-encryption between remailers is fairly weak, particularly under the model where some of the servers are hostile.<div><br></div><div>I wrote, but never got completely working, a direct remailer to remailer transfer protocol. They key is that remailers should not need to know or trust each other. The key ID of the next remailer in the chain is already visible in the top header card of the Mixmaster message. The sending remailer can use that to authenticate the receiving remailer, and to manage the secure key exchange. Using PFS would be an improvement over what I was doing. The sending remailer does not care who it is sending to, as long as it is the remailer that the originating user wanted to be the next hop.</div><div><br></div><div>I really don’t think we want to get into any kind of CA structure.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>-Lance</div><div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>--</div><div>Lance Cottrell</div><div><a href="mailto:loki@obscura.com">loki@obscura.com</a></div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On Apr 25, 2014, at 4:14 AM, Jeremy Bentham Admin <<a href="mailto:jeremyadmin@anemone.mooo.com">jeremyadmin@anemone.mooo.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">SSH tunneling between remailers will be problematic. It will require<br>each remailer to have login credentials on all other remailers.<br><br>Why not instead mandate client certificates on a required TLS/SMTP link between remailers? We could put together some kind of private CA<br>signing process for the TLS certificates. I think most of us use<br>postfix on our remailers - the mechanism for doing this with postfix<br>is described here:<br><br><a href="http://www.postfix.org/TLS_README.html#client_cert_key">http://www.postfix.org/TLS_README.html#client_cert_key</a><br><br>On Thu, Apr 24, 2014 at 08:40:34PM -0500, Cypher wrote:<br><blockquote type="cite">3. Delivery will be done as it is now by Postfix/Sendmail except the connections between SMTP servers will be /encrypted/ using an SSH connection. This is a rehash of a concept originally developed by Crypto and Matt Ghio in the 1990's. The information on how to do this yourself can be obtained from the documentation on port forwarding on the SSH man page. We'll also provide documentation on how to easily set up SSH connections between remailers. YMMV.<br></blockquote><br>-- <br>Jeremy Bentham Remailer Admin<br>Key fingerprint = D7DE B0DF E6F9 9256 A070 B841 1942 840B 8743 B6B5<br>_______________________________________________<br>Remops mailing list<br>Remops@lists.mixmin.net<br>http://lists.mixmin.net/mailman/listinfo/remops<br></blockquote></div><br></div></body></html>