1995-01-18 - Re: Another problem w/Data Havens…

Header Data

From: pstemari@erinet.com (Paul J. Ste. Marie)
To: grendel@netaxs.com
Message Hash: a1551395b7a95d450cdfde29768f71fb223b228109ff7b14dace4993335481c6
Message ID: <9501182333.AA09451@eri.erinet.com>
Reply To: N/A
UTC Datetime: 1995-01-18 23:42:52 UTC
Raw Date: Wed, 18 Jan 95 15:42:52 PST

Raw message

From: pstemari@erinet.com (Paul J. Ste. Marie)
Date: Wed, 18 Jan 95 15:42:52 PST
To: grendel@netaxs.com
Subject: Re: Another problem w/Data Havens...
Message-ID: <9501182333.AA09451@eri.erinet.com>
MIME-Version: 1.0
Content-Type: text/plain


At 05:05 PM 1/17/95 -0700, Ben.Goren@asu.edu wrote:
> ... That's the main reason why I like my idea of having a trusted encryptor.
>Nobody's suggested that the current timestamp operators would be in Deep
>Doo-Doo if they timestampped some piece of thoughtcrime; why should
>somebody who encrypts be any different? ...

Quite possibly the timestampers would be in trouble, the risk for them is 
the same as the risk for the remailers and the DH operators.  As long as 
some piece of info is considered to be a thought-crime, everyone who accepts 
info from a wide range of sources is at risk.

> ... The service could even be advertised as a different form of timestamping
>(or notarizing). Not only do you get the file back signed, but you get it
>back encrypted and signed. ...

That would still be a useful service, however, but it does transfer the risk 
from the DH operator to the encryptor.  Since he isn't leaving evidence on a 
hard drive, his window of vunerability is somewhat less.

    --Paul J. Ste. Marie
      pstemari@well.sf.ca.us, pstemari@erinet.com






Thread