1996-05-22 - Re: An alternative to remailer shutdowns

Header Data

From: “E. ALLEN SMITH” <EALLENSMITH@ocelot.Rutgers.EDU>
To: markm@voicenet.com
Message Hash: 13ad743b18770bd809b9f75f5989d43aa35cd8bae855916d0e5746723a98445d
Message ID: <01I4ZLADUW968Y5IL9@mbcl.rutgers.edu>
Reply To: N/A
UTC Datetime: 1996-05-22 10:14:44 UTC
Raw Date: Wed, 22 May 1996 18:14:44 +0800

Raw message

From: "E. ALLEN SMITH" <EALLENSMITH@ocelot.Rutgers.EDU>
Date: Wed, 22 May 1996 18:14:44 +0800
To: markm@voicenet.com
Subject: Re: An alternative to remailer shutdowns
Message-ID: <01I4ZLADUW968Y5IL9@mbcl.rutgers.edu>
MIME-Version: 1.0
Content-Type: text/plain


From:	IN%"markm@voicenet.com"  "Mark M." 21-MAY-1996 02:41:22.53

>One problem I see with this is that if even one remailer operated using the
>block lists instead of permit lists, then every other remailer in the chain
>could hypothetically be held accountable for the contents of the message.
>This idea of permit lists makes sense, but I am not sure it would really solve
>anything.

	Well, that would depend on the traffic analysis defeating features
not working right. Admittedly, for the next-to-last or so remailer, they
may not work well enough anyway... but proof beyond a reasonable doubt would
be difficult. Civil suits unfortunately don't follow that standard (even for
the punishment done through punitive damages), but they do require some proof.
	-Allen





Thread