| 1 |
Mixmaster version 3 -- anonymous remailer software -- (C) 1999 Anonymizer Inc. |
Mixmaster 3.0 -- anonymous remailer software -- (C) 1999 - 2000 Anonymizer Inc. |
| 2 |
------------------------------------------------------------------------------ |
(C) 2000-2007 The Mixmaster Development Team |
| 3 |
|
------------------------------------------------------------------------------- |
| 4 |
|
|
| 5 |
PREVIEW VERSION --- WARNING: THIS SOFTWARE IS UNDER DEVELOPMENT! |
PREVIEW VERSION --- WARNING: THIS SOFTWARE IS UNDER DEVELOPMENT! |
| 6 |
|
|
| 8 |
|
|
| 9 |
* a remailer client: |
* a remailer client: |
| 10 |
|
|
| 11 |
The remailer client supports sending anonymous mail using Cypherpunk |
The remailer client supports sending anonymous mail using Cypherpunk and |
| 12 |
and Mixmaster remailers, managing pseudonyms at Newnym nym servers |
Mixmaster remailers. It supports OpenPGP encryption (compatible with PGP 2, |
| 13 |
and receiving mail anonymously from Cypherpunk remailers. It supports |
PGP 5 and up, and GnuPG). |
|
OpenPGP encryption (compatible with PGP 2, PGP 5 and up, and GnuPG). |
|
| 14 |
|
|
| 15 |
The client can be used with a menu-based user interface and with |
The client can be used with a menu-based user interface and with command line |
| 16 |
command line options. |
options. |
| 17 |
|
|
| 18 |
* a remailer: |
* a remailer: |
| 19 |
|
|
| 20 |
The remailer supports the Cypherpunk and Mixmaster message formats. |
The remailer supports the Cypherpunk and Mixmaster message formats. It can |
| 21 |
It can be integrated with the mail delivery system of Unix-based |
be integrated with the mail delivery system of Unix-based computers or use |
| 22 |
computers or use the POP3 and SMTP protocols for mail transfer. |
the POP3 and SMTP protocols for mail transfer. Mixmaster includes an |
| 23 |
Mixmaster includes an automated abuse-handling system. |
automated abuse-handling system. |
| 24 |
|
|
| 25 |
Please report any problems via the bug and patch trackers at |
Please report any problems via the bug and patch trackers at |
| 26 |
http://sourceforge.net/projects/mixmaster/ |
http://sourceforge.net/projects/mixmaster/ |
| 27 |
|
|
|
[Note: The final release of Mixmaster 3.0 will include the improved |
|
|
Mixmaster protocol version 3.] |
|
|
|
|
| 28 |
|
|
| 29 |
Installation: |
Installation: |
| 30 |
------------ |
------------ |
| 31 |
|
|
| 32 |
Libraries: |
Libraries: |
| 33 |
|
|
| 34 |
Mixmaster uses the cryptographic library OpenSSL. If you want to use |
Mixmaster requires the libraries OpenSSL, zlib, and pcre. |
| 35 |
the menu-based user interface, you also need the ncurses library. If |
|
| 36 |
these libraries are not installed on your system, get them from |
If you want to use the menu-based user interface, you also need the ncurses |
| 37 |
ftp://mixmaster.anonymizer.com/ and extract them in the Src |
library. If these libraries are not installed on your system, you will need |
| 38 |
directory first. |
to obtain the latest versions from the sources below and extract them in the |
| 39 |
|
the Src/ directory first. |
| 40 |
|
|
| 41 |
|
OpenSSL is available from http://www.openssl.org/source/ |
| 42 |
|
|
| 43 |
|
Ncurses can be obtained from http://ftp.gnu.org/pub/gnu/ncurses/ |
| 44 |
|
|
| 45 |
The Perl Compatable Regular Expressions library can be obtained from |
The Perl Compatable Regular Expressions library can be obtained from |
| 46 |
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/ |
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/ |
| 47 |
|
|
| 48 |
The zlib compression libraries can be obtained at |
The zlib compression libraries can be obtained from |
| 49 |
http://www.gzip.org/zlib/ |
http://www.gzip.org/zlib/ |
| 50 |
|
|
| 51 |
To install or upgrade Mixmaster, type `./Install'. |
To install or upgrade Mixmaster, type `./Install'. |
| 52 |
|
|
| 53 |
Mixmaster uses lists of currently operating remailers and information |
Mixmaster clients rely on pingers to compile statistics and keyrings for |
| 54 |
about their reliability. You can get the current remailer lists from |
currently operating remailers. A list of public pingers can be obtained from |
| 55 |
http://stats.melontraffickers.com/ and http://anon.efga.org/ and via |
http://www.noreply.org/allpingers/. |
| 56 |
finger from nym.alias.net: |
|
| 57 |
|
Alternatively clients can operate their own pingers to generate statistics. |
| 58 |
|
Pinger software can be obtained from http://www.palfrader.org/echolot/. If you |
| 59 |
|
choose this option, please publish the pinger results for the benefit of other |
| 60 |
|
Mixmaster users and notify the metastats maintainer at admin@mixmin.net. |
| 61 |
|
|
| 62 |
|
The required files published by pingers are:- |
| 63 |
pubring.asc Type 1 remailer keys |
pubring.asc Type 1 remailer keys |
| 64 |
pubring.mix Type 2 remailer keys |
pubring.mix Type 2 remailer keys |
| 65 |
rlist.txt List of reliable type 1 remailers |
rlist.txt List of reliable type 1 remailers |
| 66 |
mlist.txt List of reliable type 2 remailers |
mlist.txt List of reliable type 2 remailers |
| 67 |
type2.list List of known type 2 remailers (optional) |
type2.list List of known type 2 remailers (optional) |
| 68 |
|
|
|
If you wish to participate in the Remailer Abuse Blocklist, you will need |
|
|
to obtain the blocklist file from http://www.paracrypt.com/remailerabuse/ |
|
|
and place it in your Mix directory. This may be automated with cron. |
|
|
|
|
|
For support for multiple RAB services, edit the file Src/config.h manually, |
|
|
and add additional block files to the existing line, such as: |
|
|
|
|
|
#define DESTBLOCK "dest.blk rab.blk rab2.blk rab3.blk" |
|
|
|
|
|
Note that only the first file should the the local block list, as it is the |
|
|
only file mix will open for writing. Most users will not need to edit |
|
|
config.h. |
|
|
|
|
|
|
|
| 69 |
Using the remailer client: |
Using the remailer client: |
| 70 |
------------------------- |
------------------------- |
| 71 |
|
|
| 72 |
To use the menu-based user interface, simply run `mix'. To send an |
To use the menu-based user interface, simply run `mixmaster'. To send an |
| 73 |
anonymous or pseudonymous reply to a message from within your mail or |
anonymous or pseudonymous reply to a message from within your mail or news |
| 74 |
news reader, you can pipe it to `mix'. |
reader, you can pipe it to `mixmaster'. |
| 75 |
|
|
| 76 |
The interactive mode supports sending mail, manages pseudonymous |
The interactive mode supports sending mail and contains a simple mail reading |
| 77 |
accounts at nym servers and contains a simple mail reading function. |
function. OpenPGP messages are encrypted and decrypted automatically. |
| 78 |
OpenPGP messages are encrypted and decrypted automatically. It can |
|
| 79 |
also decrypt messages encrypted to ordinary non-anonymous OpenPGP keys |
In the non-interactive mode, Mixmaster reads a message from a file or from its |
| 80 |
if you use the same passphrase for the nyms as for the OpenPGP key. |
standard input. The command line options are described in the manual page |
| 81 |
|
(mixmaster.1). |
|
In the non-interactive mode, Mixmaster reads a message from a file or |
|
|
from its standard input. The command line options are described in the |
|
|
manual page (mix.1). |
|
| 82 |
|
|
| 83 |
|
|
| 84 |
Mixmaster as a remailer: |
Mixmaster as a remailer: |
| 85 |
----------------------- |
----------------------- |
| 86 |
|
|
| 87 |
The Mixmaster remailer can be installed on any account that can |
The Mixmaster remailer can be installed on any account that can receive mail. |
| 88 |
receive mail. Non-remailer messages will be delivered as usual. If |
Non-remailer messages will be delivered as usual. If you have root access, you |
| 89 |
you have root access, you may want to create a new user (e.g., |
may want to create a new user (e.g., `remailer') and install Mixmaster under |
| 90 |
`remailer') and install Mixmaster under that user id. |
that user id. |
| 91 |
|
|
| 92 |
The Install script provides a simple way to set up the remailer. More |
The Install script provides a simple way to set up the remailer. More |
| 93 |
information about configuring Mixmaster can be found in the manual |
information about configuring Mixmaster can be found in the manual page. |
| 94 |
page. Typically, incoming mail is piped to "mix -RM". In a UUCP |
Typically, incoming mail is piped to "mixmaster -RM". In a UUCP setting, it may |
| 95 |
setting, it may be useful to use just "mix -R", and run "mix -S" once |
be useful to use just "mixmaster -R", and run "mixmaster -S" once all messages |
| 96 |
all messages have arrived. |
have arrived. |
| 97 |
|
|
| 98 |
Announcing a new remailer to the public is most commonly done by posting |
Announcing a new remailer to the public is most commonly done by posting the |
| 99 |
the remailer keys and capabilities to alt.privacy.anon-server as well as |
remailer keys and capabilities to alt.privacy.anon-server as well as the |
| 100 |
the "remops" mailing list. Information about the remops list can be found |
"remops" mailing list. Information about the remops list can be found here: |
| 101 |
here: http://lexx.shinn.net/mailman/listinfo/remops |
http://lists.mixmin.net/mailman/listinfo/remops |
|
|
|
|
To upgrade from a Mixmaster 2.0.* remailer installation, make a |
|
|
backup of your keys and configuration files before you run Install. |
|
| 102 |
|
|
| 103 |
|
|
| 104 |
Installation problems: |
Installation problems: |
| 105 |
--------------------- |
--------------------- |
| 106 |
|
|
| 107 |
In case one of the libraries Mixmaster uses is installed incorrectly |
In case one of the libraries Mixmaster uses is installed incorrectly on your |
| 108 |
on your system, place the library source code (available from |
system, place the library source code (available from the locations listed |
| 109 |
ftp://mixmaster.anonymizer.com) in the Src directory, remove the old |
above) in the Src directory, remove the old Makefile, run the Install script |
| 110 |
Makefile, run the Install script again and answer `y' when asked |
again and answer `y' when asked whether to use the source code. |
| 111 |
whether to use the source code. |
|
| 112 |
|
The ncurses library can use termcap and terminfo databases. The Mixmaster |
| 113 |
The ncurses library can use termcap and terminfo databases. The |
Install script tries to find out whether terminfo is available. If you get a |
| 114 |
Mixmaster Install script tries to find out whether terminfo is |
"Can't open display" error when starting the Mixmaster menu, run "./configure |
| 115 |
available. If you get a "Can't open display" error when starting |
--enable-termcap; make lib/libncurses.a" in the ncurses directory. |
|
the Mixmaster menu, run "./configure --enable-termcap; make lib/libncurses.a" |
|
|
in the ncurses directory. |
|
| 116 |
|
|
| 117 |
|
|
| 118 |
Security notes: |
Security notes: |
| 119 |
-------------- |
-------------- |
| 120 |
|
|
| 121 |
The ciphers and the anonymizing mix-net protocol used in Mixmaster |
The ciphers and the anonymizing mix-net protocol used in Mixmaster correspond |
| 122 |
correspond to the state of the art (see the Security Considerations |
to the state of the art (see the Security Considerations section of the |
| 123 |
section of the Mixmaster Protocol specification for details). However, |
Mixmaster Protocol specification for details). However, no security proofs |
| 124 |
no security proofs exist for any practical cryptosystem. It is |
exist for any practical cryptosystem. It is unlikely that their security will |
| 125 |
unlikely that their security will be broken, but there is no "perfect |
be broken, but there is no "perfect security". Software can also contain |
| 126 |
security". Software can also contain implementation errors. The |
implementation errors. The complete Mixmaster source code is available for |
| 127 |
complete Mixmaster source code is available for public review, so that |
public review, so that everyone can verify what the program does, and it is |
| 128 |
everyone can verify what the program does, and it is unlikely that |
unlikely that security related errors or secret back doors in the software |
| 129 |
security related errors or secret back doors in the software would go |
would go unnoticed. |
| 130 |
unnoticed. |
|
| 131 |
|
No software is secure if run in an insecure environment. For that reason you |
| 132 |
No software is secure if run in an insecure environment. For that |
must make sure that there is no malicious software (such as viruses) running on |
| 133 |
reason you must make sure that there is no malicious software (such as |
your computer. Deleted files and even passphrases can in many cases be read |
| 134 |
viruses) running on your computer. Deleted files and even passphrases |
from the hard disk if an adversary has access to the computer. The use of disk |
| 135 |
can in many cases be read from the hard disk if an adversary has |
encryption programs is recommended to avoid this risk. |
| 136 |
access to the computer. The use of disk encryption programs is |
|
| 137 |
recommended to avoid this risk. |
Anonymous messages are secure as long as at least one of the remailers you use |
| 138 |
|
in a chain is honest. You can use up to 20 remailers in a chain, but |
| 139 |
Anonymous messages are secure as long as at least one of the remailers |
reliability and speed decrease with longer chains. Four is a reasonable number |
| 140 |
you use in a chain is honest. You can use up to 20 remailers in a |
of remailers to use. Many remailer operators sign their keys. You should verify |
| 141 |
chain, but reliability and speed decrease with longer chains. Four is |
those signatures with OpenPGP to make sure that you have the actual remailer |
| 142 |
a reasonable number of remailers to use. Many remailer operators sign |
keys. |
| 143 |
their keys. You should verify those signatures with OpenPGP to make |
|
| 144 |
sure that you have the actual remailer keys. |
Anonymous keys usually cannot be introduced to the OpenPGP web of trust without |
| 145 |
|
giving up anonymity. For that reason, this client will use any OpenPGP key |
| 146 |
Anonymous keys usually cannot be introduced to the OpenPGP web of |
found on the key ring, whether it is certified or not. Your key ring must not |
| 147 |
trust without giving up anonymity. For that reason, this client will |
contain any invalid keys when used with this program. |
| 148 |
use any OpenPGP key found on the key ring, whether it is certified or |
|
| 149 |
not. Your key ring must not contain any invalid keys when used with |
If you want to use a pseudonym, the client will ask you for a passphrase to |
| 150 |
this program. |
protect the nym database. Your passphrase should be long, and hard to guess. |
| 151 |
|
Anyone who gets hold of your nym database and private keys and can determine |
| 152 |
If you want to use a pseudonym, the client will ask you for a |
the passphrase will be able to compromise your pseudonymous identities. Note |
| 153 |
passphrase to protect the nym database. Your passphrase should be |
that some operating systems may store your passphrase on your hard disk in |
| 154 |
long, and hard to guess. Anyone who gets hold of your nym database and |
clear. |
| 155 |
private keys and can determine the passphrase will be able to |
|
| 156 |
compromise your pseudonymous identities. Note that some operating |
While a good client passphrase can protect your keys if someone gets hold of |
| 157 |
systems may store your passphrase on your hard disk in clear. |
your files, the remailer passphrase offers only casual protection for the |
| 158 |
|
remailer keys. If you install a remailer, the remailer passphrase must be |
| 159 |
While a good client passphrase can protect your keys if someone gets |
different from your private passphrases. |
|
hold of your files, the remailer passphrase offers only casual |
|
|
protection for the remailer keys. If you install a remailer, the |
|
|
remailer passphrase must be different from your private passphrases. |
|
| 160 |
|
|
| 161 |
|
|
| 162 |
Copyright: |
Copyright: |
| 163 |
--------- |
--------- |
| 164 |
|
|
| 165 |
Mixmaster may be redistributed and modified under certain conditions. |
Mixmaster may be redistributed and modified under certain conditions. This |
| 166 |
This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF |
software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, |
| 167 |
ANY KIND, either express or implied. See the file COPYRIGHT for |
either express or implied. See the file COPYRIGHT for details. |
| 168 |
details. |
|
| 169 |
|
A license is required to use the IDEA(TM) algorithm for commercial purposes; |
| 170 |
A license is required to use the IDEA(TM) algorithm for commercial |
see the file idea.txt for details. |
| 171 |
purposes; see the file idea.txt for details. |
|
| 172 |
|
Mixmaster uses the compression library zlib by Jean-loup Gailly and Mark Adler, |
| 173 |
Mixmaster uses the compression library zlib by Jean-loup Gailly and Mark |
the free ncurses library and the regex library by Philip Hazel. This product |
| 174 |
Adler, the free ncurses library and the regex library by Philip Hazel. |
includes cryptographic software written by Eric Young (eay@cryptsoft.com). This |
| 175 |
This product includes cryptographic software written by Eric Young |
product includes software developed by the OpenSSL Project for use in the |
| 176 |
(eay@cryptsoft.com). This product includes software developed by the |
OpenSSL Toolkit (http://www.OpenSSL.org/). For some platforms: This product |
| 177 |
OpenSSL Project for use in the OpenSSL Toolkit (http://www.OpenSSL.org/). |
includes software developed by the University of California, Berkeley and its |
| 178 |
For some platforms: This product includes software developed by the |
contributors. |
|
University of California, Berkeley and its contributors. |
|
| 179 |
|
|
| 180 |
All trademarks are the property of their respective owners. |
All trademarks are the property of their respective owners. |
| 181 |
|
|
| 182 |
$Id: README,v 1.5 2002/08/13 23:36:44 rabbi Exp $ |
$Id$ |