1996-08-27 - Re: File System Encryption

Header Data

From: “Douglas R. Floyd” <dfloyd@io.com>
To: drifter@c2.net (Drifter)
Message Hash: c510fc23f40a7002fc91576a87394694167af191134943cc13fa4c72c20b0e60
Message ID: <199608271401.JAA04116@xanadu.io.com>
Reply To: <3221922d.3171340@c2.org>
UTC Datetime: 1996-08-27 17:38:19 UTC
Raw Date: Wed, 28 Aug 1996 01:38:19 +0800

Raw message

From: "Douglas R. Floyd" <dfloyd@io.com>
Date: Wed, 28 Aug 1996 01:38:19 +0800
To: drifter@c2.net (Drifter)
Subject: Re: File System Encryption
In-Reply-To: <3221922d.3171340@c2.org>
Message-ID: <199608271401.JAA04116@xanadu.io.com>
MIME-Version: 1.0
Content-Type: text/plain


> 
> I'm aware of the three main disk encryption programs SFS, SECDRV, and
> SECDEV, but I need to find a solution that works with Windows 95 32bit
> or Windows NT 4.0.
> 
> I'm currently using SFS 1.17 and Secure Drive under Win-95, but am
> unable to continue to work in dos compatability mode due to severe
> performance hits.  I am open to commercial products that have passed
> peer review, but know of none.
> 
> If anyone could suggest a solution (outside of switching OS's), I
> would be *most* gratefull.
> 
> Please respond to the list, as I am a subscriber under another
> account.

If you have another 386 or 486 lying around, you could install Linux and
Ian's encrypted loopback code on a remote box, then NFS or Samba the
filesystem over.  For protection, you could modify the vlock command to
lock the console (and not unlock it), and disable inetd.  Then, unless
someone has the permissions to access the files through the network, the
files are inaccessable ;-).

> 
> The Drifter
> 






Thread