<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">You are talking specifically about Remix situations, rather than standard Mixmaster behavior?<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; font-size: medium; "><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 Jul 10, 2012, at 2:20 PM, Mike Mestnik wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>I know this is a few years late, but setting up Mixmaster I encountered<br>a few problems in the software and protocol.<br><br>Simply put mixmaster may not handle mixed messages being passed into the<br>mixmaster client side appropriately. What should happen in that case is<br>to decrement the TTL and forward the message to the node the msg is<br>current encrypted for. What happens, I guess, is that the message is<br>being re-mixed. In the event of a mail loop that means a message could<br>be mixed to pass through many hundreds of nodes. It accured to me that<br>Mixmaster emails should have a TTL, I think it would be safe to generate<br>TTLs like so:<br><br>A for semi random value X from 12 to ~56+-10, TTL=int(156/X). I worked<br>wit hthese numbers for a while and reduced the equation down to this.<br>156 is 12*13. The end result is once chance to produce 13, 12, 11, 10.<br> Starting with 9 there is 2 chances and 7 has 3... and so fourth.<br><br>Now it's sad that there is a 1 in 50+ chance to get a 13 and in that<br>case you'll be advertising yourself as the originator. However the ppl<br>who get 12 need others to get 13 so that they can be anonymous.<br><br>However I feel it's vary important to have a TTL, regardless of the<br>tradeoff of security. Though this will require an extension onto the<br>protocol and perhaps that means a new version?<br><br>How this came about. I had nullmail installed and I ran into a<br>situation where there were no-longer any viable relay servers. Plus I'm<br>converting this server to host tor hidden services and these hidden<br>websites will need to send mail. mixmaster, I believe, will be perfect<br>for this. I configured mixmaster-smtp and pointed nullmailer at that...<br> Un-aware that mixmaster wouldn't deliver mail to SMTP servers, but<br>instead call into sendmail(nullmailer). This created a mail loop that I<br>didn't catch until after I had reconfigured mixmaster to use a local<br>instance of socat. Here is my configuration:<br><br>/etc/nullmailer/remotes:<br>localhost smtp --port=8025<br><br>/etc/mixmaster/smtp.conf: default localhost:8025<br><br>/etc/mixmaster/client.conf:<br>SMTPRELAY localhost<br>SMTPUSERNAME/SMTPPASSWORD<br><br>/etc/rc.local: # socat 2.0.0-b4 installed.<br>( set +e<br>daemon -n gmail --stop<br>daemon -n gmail -- socat -ly TCP-LISTEN:25,bind=localhost,fork,reuseaddr<br>'OPENSSL,verify=0 | SOCKS4A:smtp.gmail.com:465 | TCP:127.0.0.1:9050'<br>)<br><br>torrc: socks 127.0.0.1:9050<br>_______________________________________________<br>Remops mailing list<br><a href="mailto:Remops@lists.mixmin.net">Remops@lists.mixmin.net</a><br>http://lists.mixmin.net/mailman/listinfo/remops<br></div></blockquote></div><br></div></body></html>