<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA512<br>
<br>
I am very much in support of this proposal. The old code needs to be
retired and the move to 4096 bits completed.<br>
<br>
-Lance Cottrell<br>
<br>
On 9/15/15, 12:45 PM, Steve Crook wrote:<br>
<span style="white-space: pre;">> Hi all,<br>
><br>
> As many of you are probably aware, Mixmaster was forked in
2013 and<br>
> modified to support 4096 bit keys at the cost of reducing the
potential<br>
> maximum hops from 20 to (worst case) 10. Other improvements
were made,<br>
> either at the time or through ongoing development and
Mixmaster now<br>
> supports AES_CTR encryption and HMAC authentication. The
current packet<br>
> format is documented within the repository.<br>
><br>
> Currently there are 27 publicly advertised Remailers, of
which 10 are<br>
> running the forked code. Of these, 9 are advertising 4096
bit RSA keys.<br>
> I speculate that there are a number of reasons why more have
not<br>
> migrated. These include:<br>
><br>
> 1) The fork isn't recognised as the "official" version.<br>
> 2) The forked version isn't packaged for any major Linux
distros.<br>
> 3) The Remailer is running on auto-pilot.<br>
><br>
> I'd like to propose that the community addresses the first
two on this<br>
> list by recognising the fork as the current, official
Mixmaster version.<br>
> The repository resides on Github[1] and is publicly
accessible. The<br>
> Debian package, currently maintained by Colin Tuckley can be
migrated to<br>
> the forked code if this proposal is greeted favourably.
Package<br>
> maintainers for other distros will probably follow in their
own<br>
> timescales.<br>
><br>
> In terms of client compatibility, along with Mixmaster
itself,<br>
> Quicksilver and Omnimix are known to work with the forked
Mixmaster.<br>
> Indeed, their current versions are compiled against it. Very
old<br>
> clients, such as Jack B. Nymble and Private Idaho will not
work but this<br>
> is nothing new, they still rely on Mixmaster versions that
haven't been<br>
> revised in well over a decade.<br>
><br>
> I'm posting this to:-<br>
> The Mixmaster Developers List (Sourceforge)<br>
> Remops Mailing List (<a class="moz-txt-link-freetext" href="http://lists.mixmin.net">http://lists.mixmin.net</a>)<br>
> alt.privacy.anon-server (Usenet)<br>
><br>
> If discussions are favourable, I propose that we adopt the
forked Github<br>
> repository as the official Mixmaster version.<br>
><br>
> Best wishes,<br>
> Steve Crook<br>
><br>
> [1] <a class="moz-txt-link-freetext" href="https://github.com/merkinmuffley/mixmaster4096">https://github.com/merkinmuffley/mixmaster4096</a><br>
><br>
><br>
>
------------------------------------------------------------------------------<br>
><br>
><br>
> _______________________________________________<br>
> Mixmaster-devel mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Mixmaster-devel@lists.sourceforge.net">Mixmaster-devel@lists.sourceforge.net</a><br>
> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/mixmaster-devel">https://lists.sourceforge.net/lists/listinfo/mixmaster-devel</a></span><br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)<br>
Comment: GPGTools - <a class="moz-txt-link-freetext" href="http://gpgtools.org">http://gpgtools.org</a><br>
<br>
iQEcBAEBCgAGBQJV+JprAAoJEKZcnJAGU1vU+i8H/iPSDIOjC44tgiFYlcHo5wS6<br>
6EJ3HVBCGvWxbjrwSAxHAoPyNrxDJX4RJAH+3tGWW+Kq1PxRcDbb0sN9pdVVPLdq<br>
VETpg4uwjF1Mu1mQmM+TUFbxuSPSbtzR44eST+fAwBQJGjjNycyL5l/EvvdIvwJD<br>
O9WHbFOyr/KGMqTiqDZfUp3X1iI6+ObJf7v94PuxpHcIdGKBtxxBTuWAJB2FPWu+<br>
4hgTWZWjJpJQYt/FlumuS+w5zcgRiFBC5hswlz5WUIpzBTi1+lNKUAXVRQQNW98K<br>
gIeH57+dhrdhuXzvC6MROh66CMJjj7qsAygCk3Ess1d3snCziMuVjlwYBDUEde4=<br>
=OuAr<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>