| 1 |
rabbi |
200 |
Subject: Instructions for using anonymous remailer |
| 2 |
|
|
|
| 3 |
|
|
This message is being sent to you automatically in response to the message |
| 4 |
|
|
you sent to remailer@nately.ucsd.edu with subject "remailer-help". |
| 5 |
|
|
This help file is a barely modified version of the help file written by |
| 6 |
|
|
Matthew Ghio. |
| 7 |
|
|
|
| 8 |
|
|
This file describes how to use this remailer as a type 1 remailer. |
| 9 |
|
|
It is capable of providing a much higher level of security if |
| 10 |
|
|
you use the correct software to produce the messages. |
| 11 |
|
|
This software is available from ftp://nately.ucsd.edu/pub/remail |
| 12 |
|
|
Read the README file for instructions. This file is export restricted, |
| 13 |
|
|
so it can not be retrieved directly. |
| 14 |
|
|
|
| 15 |
|
|
I have an automated mail handling program installed on my account |
| 16 |
|
|
mixmaster@nately.ucsd.edu which will take any message with the proper headers |
| 17 |
|
|
and automatically re-send it anonymously. You can use this by sending a message |
| 18 |
|
|
to mixmaster@nately.ucsd.edu, with the header Anon-To: <address>, the address |
| 19 |
|
|
that you want to send anonymously to. If you can't add headers to your mail, |
| 20 |
|
|
you can place two colons on the first line of your message, and then the Anon-To |
| 21 |
|
|
line. Follow that with a blank line, and then begin your message. |
| 22 |
|
|
For Example: |
| 23 |
|
|
|
| 24 |
|
|
> From: joe@site.com |
| 25 |
|
|
> To: mixmaster@nately.ucsd.edu |
| 26 |
|
|
> Subject: Anonymous Mail |
| 27 |
|
|
> |
| 28 |
|
|
> :: |
| 29 |
|
|
> Anon-To: beth@univ.edu |
| 30 |
|
|
> |
| 31 |
|
|
> This is some anonymous mail. |
| 32 |
|
|
|
| 33 |
|
|
The above would be delivered to beth@univ.edu anonymously. All headers in |
| 34 |
|
|
the original message are removed, with the exception of the Subject (and |
| 35 |
|
|
Content-Type, if present). She would not know that it came from Joe, nor |
| 36 |
|
|
would she be able to reply to the message. However, there are a few ways |
| 37 |
|
|
that the true identity of the sender could be found. First, if many |
| 38 |
|
|
anonymous messages were sent, someone could compare the times that the |
| 39 |
|
|
messages were sent with the times that 'joe' was logged in. However, this |
| 40 |
|
|
can be prevented by instructing the remailer to delay the message, by using |
| 41 |
|
|
the Latent-Time header: |
| 42 |
|
|
|
| 43 |
|
|
> From: joe@site.com |
| 44 |
|
|
> To: mixmaster@nately.ucsd.edu |
| 45 |
|
|
> Subject: Anonymous Mail |
| 46 |
|
|
> |
| 47 |
|
|
> :: |
| 48 |
|
|
> Anon-To: beth@univ.edu |
| 49 |
|
|
> Latent-Time: +1:00 |
| 50 |
|
|
> |
| 51 |
|
|
> This is some anonymous mail. |
| 52 |
|
|
|
| 53 |
|
|
The message would be delayed one hour from when it is sent. |
| 54 |
|
|
|
| 55 |
|
|
This remailer also holds all incoming messages in a pool. Once every 10 min, |
| 56 |
|
|
the remailer checks to see if new messages have arrived. If so, random |
| 57 |
|
|
messages are selected from the pool and sent on, leaving the pool the origonal |
| 58 |
|
|
size (at this time, five messages). This provides reordering, generaly thought |
| 59 |
|
|
to be more reliable than latency alone. |
| 60 |
|
|
|
| 61 |
|
|
Another problem is that some mailers automatically insert a signature file. |
| 62 |
|
|
Of course, this usually contains the senders email address, and so would |
| 63 |
|
|
reveal their identity. The remailer software can be instructed to remove |
| 64 |
|
|
a signature file with the header "Cutmarks". Any line beginning with the |
| 65 |
|
|
same text at in the cutmarks header, and any lines following it will be |
| 66 |
|
|
removed. |
| 67 |
|
|
|
| 68 |
|
|
> From: sender@origin.com |
| 69 |
|
|
> To: mixmaster@nately.ucsd.edu |
| 70 |
|
|
> Subject: Anonymous Mail |
| 71 |
|
|
> |
| 72 |
|
|
> :: |
| 73 |
|
|
> Anon-To: recipient@destination.com |
| 74 |
|
|
> Cutmarks: -- |
| 75 |
|
|
> |
| 76 |
|
|
> This line of text will be in the anonymous message. |
| 77 |
|
|
> -- |
| 78 |
|
|
> This line of text will not be in the anonymous message. |
| 79 |
|
|
|
| 80 |
|
|
The remailer can also be used to make posts to usenet. To do this, use |
| 81 |
|
|
Anon-Post-To. Non-Anonymous posts can be made by using Post-To. |
| 82 |
|
|
|
| 83 |
|
|
|
| 84 |
|
|
> From: poster@origin.com |
| 85 |
|
|
> To: mixmaster@nately.ucsd.edu |
| 86 |
|
|
> Subject: Anonymous Post |
| 87 |
|
|
> |
| 88 |
|
|
> :: |
| 89 |
|
|
> Anon-Post-To: alt.test |
| 90 |
|
|
> |
| 91 |
|
|
> This is an anonymous message |
| 92 |
|
|
|
| 93 |
|
|
You can add additional headers to the output message by preceeding them |
| 94 |
|
|
with ## |
| 95 |
|
|
|
| 96 |
|
|
> From: chris@nifty.org |
| 97 |
|
|
> To: mixmaster@nately.ucsd.edu |
| 98 |
|
|
> Subject: Nifty Anon Msg |
| 99 |
|
|
> |
| 100 |
|
|
> :: |
| 101 |
|
|
> Anon-To: andrew@where-ever.org |
| 102 |
|
|
> |
| 103 |
|
|
> ## |
| 104 |
|
|
> Reply-To: acs-314159@chop.ucsd.edu |
| 105 |
|
|
> |
| 106 |
|
|
> A Message with a reply address. |
| 107 |
|
|
|
| 108 |
|
|
For added security, you can encrypt your messages to the remailer with PGP. |
| 109 |
|
|
The remailer software will decrypt the message and send it on. Here is the |
| 110 |
|
|
remailer's public key: |
| 111 |
|
|
|
| 112 |
|
|
|
| 113 |
|
|
-----BEGIN PGP PUBLIC KEY BLOCK----- |
| 114 |
|
|
Version: 2.6 |
| 115 |
|
|
|
| 116 |
|
|
mQBNAy7MYUgAAAECAKennY9a57JPJZMFpD0G90iXaZRPNNxgtbKcJR//KByvyI/7 |
| 117 |
|
|
hIGI8WMpReHIu6diP4FxsCXjzE+5idqkz6eP42EABRG0Lk1peG1hc3RlciByZW1h |
| 118 |
|
|
aWxlciA8bWl4bWFzdGVyQG5hdGVseS51Y3NkLmVkdT4= |
| 119 |
|
|
=KlNO |
| 120 |
|
|
-----END PGP PUBLIC KEY BLOCK----- |
| 121 |
|
|
|
| 122 |
|
|
To utilize this feature, create a message with two colons on the first line, |
| 123 |
|
|
then the Anon-To line, then any other headers, such as cutmarks or latency, |
| 124 |
|
|
then a blank line, and then the message. Encrypt this with the remailer's |
| 125 |
|
|
public key. Then send it to the remailer, adding the header "Encrypted: PGP". |
| 126 |
|
|
If you forget this, the remailer won't know that it needs to be decrypted. |
| 127 |
|
|
|
| 128 |
|
|
> To: mixmaster@nately.ucsd.edu |
| 129 |
|
|
> From: me@mysite.org |
| 130 |
|
|
> |
| 131 |
|
|
> :: |
| 132 |
|
|
> Encrypted: PGP |
| 133 |
|
|
> |
| 134 |
|
|
> -----BEGIN PGP MESSAGE----- |
| 135 |
|
|
> Version: 2.3a |
| 136 |
|
|
> |
| 137 |
|
|
> hIkCuMeAjnwmCTUBA+dfWcFk/fLRpm4ZM7A23iONxkOGDL6D0FyRi/r0P8+pH2gf |
| 138 |
|
|
> HAi4+1BHUhXDCW2LfLfay5JwHBNMtcdbgXiQVXIm0cHM0zgf9hBroIM9W+B2Z07i |
| 139 |
|
|
> 6UN3BDhiTSJBCTZUGQ7DrkltbgoyRhNTgrzQRR8FSQQXSo/cf4po0vCezKYAAABP |
| 140 |
|
|
> smG6rgPhdtWlynKSZR6Gd2W3S/5pa+Qd+OD2nN1TWepINgjXVHrCt0kLOY6nVFNQ |
| 141 |
|
|
> U7lPLDihXw/+PPJclxwvUeCSygmP+peB1lPrhSiAVA== |
| 142 |
|
|
> =da+F |
| 143 |
|
|
> -----END PGP MESSAGE----- |
| 144 |
|
|
|
| 145 |
|
|
Any unencrypted text after the PGP message is also remailed. This is to allow |
| 146 |
|
|
sending to someone who is anonymous. If you create a PGP-encrypted message to |
| 147 |
|
|
yourself via my remailer, and then you give it to someone, they can send you a |
| 148 |
|
|
message by sending the encrypted message to the remailer. The remailer will |
| 149 |
|
|
then decrypt it and send it to you. The message gets anonymized in the |
| 150 |
|
|
process, so the sender will need to include a return address if he wants a |
| 151 |
|
|
reply. |
| 152 |
|
|
|
| 153 |
|
|
Remailers can be chained together for additional security. |
| 154 |
|
|
If you have PGP installed on your machine, you can use my remailer |
| 155 |
|
|
chaining script (which you can get from http://nately.ucsd.edu/~loki/Welcome.html) |
| 156 |
|
|
to rout your mail through several remailers, encrypting the message to each one |
| 157 |
|
|
on the way (if it supports PGP). |
| 158 |
|
|
|
| 159 |
|
|
Traffic is important to the security of remailers. To make traffic analysis |
| 160 |
|
|
more difficult, this remailer will accept messages to be trashed. Any |
| 161 |
|
|
message asking to be remailed to null will be trashed. |
| 162 |
|
|
|
| 163 |
|
|
> From: chris@nifty.org |
| 164 |
|
|
> To: mixmaster@nately.ucsd.edu |
| 165 |
|
|
> Subject: Trash this |
| 166 |
|
|
> |
| 167 |
|
|
> :: |
| 168 |
|
|
> Anon-To: null |
| 169 |
|
|
> |
| 170 |
|
|
> Random junk |
| 171 |
|
|
|
| 172 |
|
|
This can (and probably should) be sent encrypted with PGP. Using the |
| 173 |
|
|
"Encrpyted: PGP" command |
| 174 |
|
|
|
| 175 |
|
|
Abuse Policy: |
| 176 |
|
|
I consider the following to be inappropriate use of this anonymous remailer, |
| 177 |
|
|
and will take steps to prevent anyone from doing any of the following: |
| 178 |
|
|
- Sending messages intended primarilly to be harassing or annoying. |
| 179 |
|
|
- Use of the remailer for any illegal purpose. |
| 180 |
|
|
If you don't want to receive anonymous mail, send me a message, and I will |
| 181 |
|
|
add your email address to the block list. |
| 182 |
|
|
|
| 183 |
|
|
You can get a list of statistics on remailer usage by sending mail to |
| 184 |
|
|
mixmaster@nately.ucsd.edu with Subject: remailer-stats |
| 185 |
|
|
|
| 186 |
|
|
|