1995-01-13 - Re: essential characteristics of a Data Haven

Header Data

From: eric@remailer.net (Eric Hughes)
To: cypherpunks@toad.com
Message Hash: 29fef88defa1afa205aa10fd44626b291c4aa43ee7fd7e99b7bb1eec21045a91
Message ID: <199501131807.KAA02940@largo.remailer.net>
Reply To: <Pine.NXT.3.91.950112180625.3304B-100000@kisa>
UTC Datetime: 1995-01-13 18:09:41 UTC
Raw Date: Fri, 13 Jan 95 10:09:41 PST

Raw message

From: eric@remailer.net (Eric Hughes)
Date: Fri, 13 Jan 95 10:09:41 PST
To: cypherpunks@toad.com
Subject: Re: essential characteristics of a Data Haven
In-Reply-To: <Pine.NXT.3.91.950112180625.3304B-100000@kisa>
Message-ID: <199501131807.KAA02940@largo.remailer.net>
MIME-Version: 1.0
Content-Type: text/plain


   From: Adam Feuer <adamfast@seanet.com>

   what differentiates a "data haven" from "reasonably secure offsite
   storage"?

Right now, that's easy.  Data havens don't exist, and prototype code
for reasonably secure off-site storage does.

The key distinguishing feature of off-site storage is that it stores
data only as bits, structured and segmented, but not interpreted _as_
anything but bits.  A data haven, on the other hand, holds things that
someone disapproves of, otherwise there's no need for a haven.  _A
fortiori_, if someone disapproves of it, it must mean something.  Raw
bits don't mean anything, or rather, they can mean everything.

Eric





Thread