cryptoanarchy.wiki

Arise, you have nothing to lose but your barbed wire fences!

1995-10-27 - Re: New release of CFS Unix encrypting file system available

Header Data

From: Matt Blaze <mab@crypto.com>
To: Scott Brickner <sjb@universe.digex.net>
Message Hash: cafb430181e7f0b2f5a457ffc4c37e00fb1f82d33792d977b15d91c42399ed0a
Message ID: <199510272036.UAA28683@crypto.com>
Reply To: <199510271954.PAA20647@universe.digex.net>
UTC Datetime: 1995-10-27 20:34:56 UTC
Raw Date: Fri, 27 Oct 95 13:34:56 PDT

Raw message

From: Matt Blaze <mab@crypto.com>
Date: Fri, 27 Oct 95 13:34:56 PDT
To: Scott Brickner <sjb@universe.digex.net>
Subject: Re: New release of CFS Unix encrypting file system available
In-Reply-To: <199510271954.PAA20647@universe.digex.net>
Message-ID: <199510272036.UAA28683@crypto.com>
MIME-Version: 1.0
Content-Type: text/plain


> What happens to hard links?
> 
> mkdir foo bar
> CFS_set_directory_key -directory ./foo -key foo-key
> CFS_set_directory_key -directory ./bar -key bar-key

This isn't how it works.  You "attach" an encrypted directory to a
virtual namespace into which you write (and read) the cleartext.  It's
similar to mounting a file system.

> cp /etc/passwd ./foo/test1
> ln ./foo/footest ./bar/bartest
> cmp ./foo/footest ./bar/bartest

Hard links don't work across different "attached" directories (just as
they don't work across different file systems).

-matt

Thread