1996-05-10 - Re: Remailer in a box

Header Data

From: “E. ALLEN SMITH” <EALLENSMITH@ocelot.Rutgers.EDU>
To: loki@infonex.com
Message Hash: b1e09cc65d09d46851dc5ba741b21843006f34a5b2da386a3f4a4081f473d6c3
Message ID: <01I4IDOS8GT88Y5B50@mbcl.rutgers.edu>
Reply To: N/A
UTC Datetime: 1996-05-10 13:21:16 UTC
Raw Date: Fri, 10 May 1996 21:21:16 +0800

Raw message

From: "E. ALLEN SMITH" <EALLENSMITH@ocelot.Rutgers.EDU>
Date: Fri, 10 May 1996 21:21:16 +0800
To: loki@infonex.com
Subject: Re: Remailer in a box
Message-ID: <01I4IDOS8GT88Y5B50@mbcl.rutgers.edu>
MIME-Version: 1.0
Content-Type: text/plain


From:	IN%"loki@infonex.com"  9-MAY-1996 00:59:47.21

>This could be done with a trivial modification to the source and
>destination blocking lists (just change the sense of the checking).

	In other words, just change them from blocking to allowance? How much
technical knowledge does this take? I can see doing the incoming with procmail.

>Cyberpass (www.cyberpass.net) offers UNIX accounts without dialin access
>for $7 per month. These are available anonymously, and can be paid for with
>ecash.

	Interesting. Having ones at other than c2.org is useful for backup
purposes.

>Yes, but I only give it to remailer operators. The "bramble" might get
>flooded otherwise. Operators see the repercussions of their actions.

	Does it use how busy the remailer is to determine the approximate
frequency of the messages, or does it just keep on going with whatever you tell
it?
	Thanks,
	-Allen





Thread