1997-08-06 - Re: Eternity Uncensorable?

Header Data

From: Mark Grant <mark@unicorn.com>
To: Adam Back <aba@dcs.ex.ac.uk>
Message Hash: 92c83ed566eb6e276e026a27bc52641e91242120d1838d1bc1e6f9034edf329a
Message ID: <Pine.LNX.3.91.970806145040.16936A-100000@cowboy.dev.madge.com>
Reply To: <199708061308.OAA02171@server.test.net>
UTC Datetime: 1997-08-06 14:19:55 UTC
Raw Date: Wed, 6 Aug 1997 22:19:55 +0800

Raw message

From: Mark Grant <mark@unicorn.com>
Date: Wed, 6 Aug 1997 22:19:55 +0800
To: Adam Back <aba@dcs.ex.ac.uk>
Subject: Re: Eternity Uncensorable?
In-Reply-To: <199708061308.OAA02171@server.test.net>
Message-ID: <Pine.LNX.3.91.970806145040.16936A-100000@cowboy.dev.madge.com>
MIME-Version: 1.0
Content-Type: text/plain

On Wed, 6 Aug 1997, Adam Back wrote:

>   However this is going on other peoples information.  I don't have
>   any figures for how widespread the practice of configuring news to
>   ignore cancels is.  

Ditto. We'd have to assume that it's pretty widespread to avoid these 
> To do it properly, you'll need a local eternity server if you want to
> good security of encrypted documents. 

I'd assume that in the end this is what most people would do; get a Usenet
feed and run a server locally so that noone knows which URLs you're

> Turn of logs, and introduce forward secrecy into mixmaster.  Easy to
> do.  Why don't we have it yet?  (Ulf?  Lance?)
> Then you have as true security as you can get from a digital mix with
> the parameters mixmaster has.

That's not what I meant; I'm assuming that the mixmaster chain is pretty
secure. The problem is that when the government find 'nuclear terrorist
money-laundering kiddie drug porn' on the Eternity server they can trace
it back to the original Usenet message and then go after the remailer
operator who posted it. Making the remailers disposable or setting them up
in free countries would work, but I'd prefer a technical solution.