<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 like to avoid asking users to think too much.<div><br></div><div>It would be ideal if there were some kind of timer or something, so it could get widely deployed before starting to be used.</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 Oct 29, 2013, at 5:16 PM, <a href="mailto:lists@notatla.org.uk">lists@notatla.org.uk</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Lance Cottrell <loki <a href="http://obscura.com">obscura.com</a>> writes:<br><br><blockquote type="cite">In practice, no one uses more than a few hops for real<br>messages. I suspect that 5 is the realistic upper limit to<br>ensure reasonable delivery time and reliability. I really<br>went over the top in using 20 header blocks.<br></blockquote><br>Good thing too provided the cost was acceptable. If you'd<br>used 6 hops then halving it would get 3.<br><br><blockquote type="cite">Roll out will be a key. One does not want client software that<br>only has one or two servers through which it could route,<br>nor would one want to be one of only a few few users of the<br>new key size, since that would be easily tracked as well.<br></blockquote><br>Ease of deployment is why I've arranged my code as I have. Remailers<br>and clients don't need to update at the same time and anyone with the<br>new client remains able to use all the remailers.<br><br>You can always pick a 1024 remailer as a first hop if you don't want<br>to be recognised as a user of the new software (assuming you downloaded<br>it undetected).<br></blockquote></div><br></div></body></html>