| 315 |
<li>Installation should be complete at this point.</li> |
<li>Installation should be complete at this point.</li> |
| 316 |
</ul> |
</ul> |
| 317 |
</li> |
</li> |
| 318 |
<li>Configure your remailer through the mix.cfg file. Most options should be left alone, as they are the result of what you answered while running the Install script. If you do need to tweak these options, they are documented in the <a href=mix.manpage>mix(1)</a> manpage. NOTE: On some systems, your manpage may not install properly. If <tt>man mix</tt> cannot find a manpage, go to the directory with your source distribution, and use <tt>nroff -mandoc mix.1 | more</tt> to view the manpage. To install it permanently, copy the mix.1 file to your system's manpage directory (typically <tt>/usr/local/man/</tt>). |
<li>Configure your remailer through the mix.cfg file. Most options should be left alone, as they are the result of what you answered while running the Install script. If you do need to tweak these options, they are documented in the <a href=manpage.html>mix(1)</a> manpage. NOTE: On some systems, your manpage may not install properly. If <tt>man mix</tt> cannot find a manpage, go to the directory with your source distribution, and use <tt>nroff -mandoc mix.1 | more</tt> to view the manpage. To install it permanently, copy the mix.1 file to your system's manpage directory (typically <tt>/usr/local/man/</tt>). |
| 319 |
<li>Customize your *.txt files. Go to the directory you installed Mixmaster in and individually edit abuse.txt, blocked.txt, help.txt, reply.txt, and usage.txt to your liking; you probably won't need to do much, as the standard files are very good. Next, sign all of these files, to prove to any recipients of these messages that you are the one who sent them. The typical command is <tt>gpg --sign abuse.txt</tt>; make sure you replace the unsigned file with the signed one after you've done this. |
<li>Customize your *.txt files. Go to the directory you installed Mixmaster in and individually edit abuse.txt, blocked.txt, help.txt, reply.txt, and usage.txt to your liking; you probably won't need to do much, as the standard files are very good. Next, sign all of these files, to prove to any recipients of these messages that you are the one who sent them. The typical command is <tt>gpg --sign abuse.txt</tt>; make sure you replace the unsigned file with the signed one after you've done this. |
| 320 |
<li>Sign your remailer's public key, the adminkey.txt file, using the same procedure as above.</li> |
<li>Sign your remailer's public key, the adminkey.txt file, using the same procedure as above.</li> |
| 321 |
<li>Setup your remailing strategy. This is controlle through your SENDPOOLTIME, POOLSIZE, RATE, IDEXP, and PACKETEXP values in mix.cfg. The first two values should be set higher for greater latency in your remailer. RATE can be lowered if you are worried about floods; since this determines the percent of messages that go out each mailing, setting a lower number here slows output of messages that have flooded into your remailer. PACKETEXP determines how long you hold onto partial messages while waiting for their other pieces to come in; a long value here is probably good. IDEXP determines how long a list of message IDs is kept, to help prevent replay attacks; while this cannot be set below 5 days, it is probably a good idea to have a low value here, since legitimate messages should have almost no ID duplication.<li> |
<li>Setup your remailing strategy. This is controlle through your SENDPOOLTIME, POOLSIZE, RATE, IDEXP, and PACKETEXP values in mix.cfg. The first two values should be set higher for greater latency in your remailer. RATE can be lowered if you are worried about floods; since this determines the percent of messages that go out each mailing, setting a lower number here slows output of messages that have flooded into your remailer. PACKETEXP determines how long you hold onto partial messages while waiting for their other pieces to come in; a long value here is probably good. IDEXP determines how long a list of message IDs is kept, to help prevent replay attacks; while this cannot be set below 5 days, it is probably a good idea to have a low value here, since legitimate messages should have almost no ID duplication.<li> |
Parent Directory
| 
Revision Log
| 
Patch