Email and post to Google Groups (USENET) using secure GPG encrypted messages over an open, unencrypted channel. Works for text, photos, video. Details at Post to USENET using anonymous, GPG/PGP encrypted email (#iranelection #neda) - soc.culture.iranian | Google Groups. #iranelection
Truncated Instructions if Google not Available How to post to Google Groups (old USENET) and send email anonymously using GPG encryption and anonymous remailer chains (see also How to Send an Anonymous Email Message - About Email). If done thoughtfully and carefully, this provides a Twitter-like communications capability but with a secure (encrypted), anonymous email channel and no character limit. 1. Secure Your Message 1.0 Write your message using your text editor in the file, say, message.txt. Import any photos using the ASCII output from the uuencode command, which looks like this on Linux: % uuencode -o photo.txt my_source_photo_file.jpg my_destination_photo_name.jpg 1.1 Format your unencrypted for transmission using an anonymous remailer chain (How to Send an Anonymous Email Message - About Email, Cypherpunk Anonymous Remailer Tutorial, Bananasplit Website - Mail2News Gateway, http://feraga.com/library/howto_use_a_type_i_anonymous_remailer_cyphe... [FAQ 3.3] What is a Cypherpunk Remailer?....). If you want to post to the USENET group soc.culture.iranian on the date 2009-06-24, your message should look like this. Use this exact format -- any mistake in your formatting and the remailer will not know how to read or send your message. The Latent-Time field (hr:mn format, with a 'r' added for a random time between 0:00 and the time you specify) adds some extra time before your message is sent to hinder traffic analysis (comparing when your message was sent, which can be determined, from when it appears, which may be determined) -- use different amounts of time for each message. ------------------ begin message.txt ------------------ :: Anon-To: mail2news_nospam-20090624-soc.culture.iran...@m2n.mixmin.net Latent-Time: +0:01r ## Subject: An informative subject with hash tags (#iranelection #neda) Type your message your here, perhaps with hash tags (#iranelection #neda). Small photo attachments can be included using the uuencode-d ASCII text from the file photo.txt above: begin 644 my_destination_photo_name.jpg M+2TM+2U"14=)3B!01U`@34534T%'12TM+2TM"E9E<G-I;VXZ($=N=5!'('8Q ` end ------------------- end message.txt ------------------- 1.2 Encryption Chain for Anonymous Remailers 1.2.1 First Encryption. The message above will be emailed and posted anonymously when it is sent to one of the anonymous remailers, BUT IT IS NOT SECURE -- anyone monitoring your internet connection can intercept it. To securely encrypt your message, you'll need to use the public key from one of the anonymous remailers to which you will email your message. Look at the most recent remailer reliability statistics (Google "Remailer Reliability Stats", Cypherpunk Remailers [noreply], Cypherpunk Remailers [Randseed Pinger]), choose a reliable one based upon (1) the flag pgponly in their $remailer properties list; (2) their previous history. Retrieve the remailer's key by sending it the email, say: To: mixmas...@remailer.cyberiade.it Subject: remailer-key <No body> Some remailer choices are: mixmas...@remailer.cyberiade.it remai...@mangrin.org a...@remailer.gabrix.ath.cx mixmas...@firenze.linux.it remai...@kroken.dynalias.com If the remailer is up, you should receive, probably in a few seconds to a few hours, the message: ------------------ begin text ------------------ $remailer{"cyberiad"} = "<mixmas...@remailer.cyberiade.it> cpunk max mix pgp pgponly repgp remix latent hash cut test ek ekx esub inflt50 rhop5 reord post"; Here is the RSA PGP key: Type Bits/KeyID * * Date * * * User ID pub *1024R/7DFEC1B9 2006-09-11 Cyberiade.it Anonymous Remailer <mixmas...@remailer.cyberiade.it> -----BEGIN PGP PUBLIC KEY BLOCK----- Version: Mixmaster 3.0b2 (OpenPGP module) mQCNA0UE/x4AAAEEAKe6Oc1dgcLcWgZW2CbxmoQWFoKeOAJOwrjb5cYUv8+Q92h2 =GV1H -----END PGP PUBLIC KEY BLOCK----- Here is the DSA PGP key: *. . . . . . . . . . . . . . . . . . . . . . . . ------------------- end text ------------------- The "PGP PUBLIC KEY BLOCK" is the digital key you will use to "lock" (encrypt) your message. The remailer has a secret, unique, tightly held, PRIVATE key block that is the only key that can be used to "unlock" (decrypt) your message. This remailer uses a 1024 bit key, which is very difficult to break. Save the remailer's email reply to a file, say, key.txt. Now use GPG to import the remailers key into your keychain and encrypt your message to send to the remailer mixmas...@remailer.cyberiade.it with the (Linux) command: % gpg --import key.txt % gpg -ea --recipient mixmas...@remailer.cyberiade.it --output message.txt.gpg message.txt (Answer 'y' to the GPG queries about the authenticity of the key if you obtained it over an anonymous proxy.) The only people that will be able to decrypt this encrypted message are those who have access to the remailer's *private* key (*not* the public key that you just used to encrypt, or someone who has the resources to break this cryptographically strong PGP code.) If you use two or more remailers, no remailer will be able to determine simultaneously the source of the message and its content, and only the last remailer in the chain will have access to the message itself. 1.2.2 First Remailer Message. Format your encrypted message to send to the anonymous remailer. You should *only* use remailers that accept "pgponly" -- any unencrypted email sent to these remailers will be ignored. *The message body to the pgponly remailer (in this case mixmas...@remailer.cyberiade.it) should look like: ------------------ begin message.txt ------------------ :: Encrypted: PGP -----BEGIN PGP MESSAGE----- Version: GnuPG v1.4.3 (GNU/Linux) hIwDNeUtHbne9DkBA/9drtL/O0VOtn/dZzAw6HEdESj+sY/kwpm6941T3TzbZWKw nJM8785ZEtXQ03qGEMx/J29MgGxFTgeQjOiKmosjJibTyboppu9Jd8dEmKAjwJVh =xS0h -----END PGP MESSAGE----- ------------------- end message.txt ------------------- 1.2.3 Second Encryption. For additional security, you can repeat the first encryption process with a *second* independent, anonymous remailer, preferably from another country. Your encrypted message will first be sent to the second remailer, decrypted by it, (revealing the encrypted text above for the first remailer), sent to the first remailer, decrypted, then sent to your original Anon-To: recipient, in this case a mail2news gateway that will result in a post on Google Groups. This second encryption process can be repeated the third, fourth, etc. time, but a remailer chain more than two or three links long is more likely to break, resulting in the loss of your message, and will have a longer latency. For the second encryption, choose another remailer, say, remai...@mangrin.org, get their key, import it to your keychain, and encrypt the following message, pasted from the one immediately above: ------------------ begin message.txt ------------------ :: Anon-To: mixmas...@remailer.cyberiade.it Latent-Time: +0:02r :: Encrypted: PGP -----BEGIN PGP MESSAGE----- Version: GnuPG v1.4.3 (GNU/Linux) hIwDNeUtHbne9DkBA/9drtL/O0VOtn/dZzAw6HEdESj+sY/kwpm6941T3TzbZWKw =xS0h -----END PGP MESSAGE----- ------------------- end message.txt ------------------- % gpg --import key.txt % gpg -ea --recipient remai...@mangrin.org --output message.txt.gpg message.txt 1.2.4 Second Remailer Message. Format your encrypted message to send to the second anonymous remailer, in this example to remai...@mangrin.org. The email message should look like: To: remai...@mangrin.org Subject: <empty> ------------------ begin body ------------------ :: Encrypted: PGP -----BEGIN PGP MESSAGE----- Version: GnuPG v1.4.3 (GNU/Linux) hIwDOzGW2RFRuwkBA/96M+wsYKTu027x4VfFoJH16nG2DfWQsv8g85zXo7fcbc21 =ohYQ -----END PGP MESSAGE----- ------------------- end body ------------------- 2. From your mail server across an anonymous proxy server, email the encrypted message you created in step 1.2.4. If you formatted everything correctly and the remailers and mail2news gateway are up, your message should appear after the cumulative latency that you specified in your encrypted messages. This post was generated in exactly this way, which, if you are reading it, is proof that it works.
White space important The reader ate all the white space, which is important for the directives to the remailer! The :: and ## directives in the examples above must all be followed by a blank line or more like this. Do not send a ## Subject: line to a pgponly remailer -- the remailer will ignore the message. :: Anon-To: mail2news_nospam-20090624-soc.culture.iran...@m2n.mixmin.net Latent-Time: +0:01r ## Subject: An informative subject with hash tags (#iranelection #neda) :: Encrypted: PGP Message.
