// COMPLETE THREAD

ANON: mail concerns

2 expanded posts ยท every known parent and child

NODE 5294597aANON: mail concerns
-----BEGIN PGP SIGNED MESSAGE-----

Hm.. there have been some concerns over anonymous mail recently...
both Alan and Thomas have noted that it is easy to match up sender and
destination for a remailer which processes each message as it arrives.

Solution: cache all messages and process them later (once a day, once
a week, etc.).  For example, the remailer at elee9sf@menudo.uh.edu
caches all incoming requests, and processes them (randomly) at
midnight.

I didn't even have to modify the remailer scripts to do this; rather,
I wrote some extra ones.  The process seems stable.  The trickiest
part is scheduling the remailing: I have to use the 'at' command since
I can't have my own crontab.

Also, Thomas mentioned what seems to be 'random remailing'.  As I
mentioned in a previous message ("ANON: anonymous mail"), forcing mail
to progress through a network randomly also forces the final
destination to be known to everybody, where before only one site knows
the final destination.

Also, instead of building the necessay headers to hop mail you may be
able to use one of several scripts and programs available at
soda.berkeley.edu

Karl Barrus
<klbarrus@owlnet.rice.edu>

-----BEGIN PGP SIGNATURE-----
Version: 2.3a

iQCVAgUBLNbQEoOA7OpLWtYzAQEe0QP+KaDWOyep8+wSfEMtUjBOj8OGJMrdSCkO
jAfS3zW/uASpOfZ8zgaGBhl8kFPzF9ZyEJyKV/tydIHJdQUEI9K3FU0AE4vB2Fei
xcGcM16dZlSSOW/E+CkRR/3UstlRwUuHCccFACTh5SIPIG3mSSVvNMEp7Cz+SIss
j5Mkq9KqJc0=
=tWzv
-----END PGP SIGNATURE-----
NODE 2cdaa600Re: ANON: mail concerns
I recently bought a copy of oracom's "Programing Perl" (which btw has a
GREAT quickreference guide) and have been working on a remailer mod with
little succsess. My thought goes like this:
New remailer command...
::
Induce-Delay: X

Where X is any number between 0 and 9999, or the word 'Random'. This would
delay the remailing of the message by X minutes through a simple perl
sleep command. 

QUESTION: Would new mail be kept waiting by the old mail? Or would Unix
spawn a new incarnation of the remailer process to take care of each
subsequent message?

::
Mail-At-Time: X
Mail-On-Date: X

Again both of these would use a sleep command to avoid the cron and at
commands.

::
Request-Encryption-To: X

If user ID X is on the remailer's pubkey ring, the outgoing message is
encrypted to X. This could be usefull for anonymous return-address blocks.

I think these are all pretty good ideas, however I'm not very good at perl
(in fact, at this point I suck) and things keep on bombing.

Well, Happy Hunting to all, -Chris.

Christian Douglas Odhner     | "The NSA can have my secret key when they pry
cdodhner@indirect.com	     | it from my cold, dead, hands... But they shall
pgp 2.3 public key by finger | NEVER have the password it's encrypted with!"
My opinions are shareware. To register your copy, send me 15$ in DigiCash.
  Key fingerprint =  58 62 A2 84 FD 4F 56 38  82 69 6F 08 E4 F1 79 11