From mboxrd@z Thu Jan  1 00:00:00 1970
From: Hans Reiser <reiser@namesys.com>
Subject: Re: Reiser4 crypto-compression design
Date: Thu, 27 Mar 2003 19:30:11 +0300
Message-ID: <3E832713.6050004@namesys.com>
References: <3E80B384.2190B074@namesys.com> <200303260730.34330.phma@webjockey.net> <87isu527di.fsf@labatt.uhoreg.ca> <200303261916.37039.phma@webjockey.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <reiserfs-list-return-13407-reiserfs=m.gmane.org@namesys.com>
list-help: <mailto:reiserfs-list-help@namesys.com>
list-unsubscribe: <mailto:reiserfs-list-unsubscribe@namesys.com>
list-post: <mailto:reiserfs-list@namesys.com>
Errors-To: flx@namesys.com
In-Reply-To: <200303261916.37039.phma@webjockey.net>
List-Id: <reiserfs-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: Pierre Abbat <phma@webjockey.net>
Cc: reiserfs-list@namesys.com

Pierre Abbat wrote:

>On Wednesday 26 March 2003 15:35, Hubert Chan wrote:
>  
>
>>A related, but different question, which may have already been answered
>>by Edward's document: can a directory be encrypted, so that only a user
>>with the password can list its contents?
>>    
>>
>
>The way that's done in CFS is that the filenames are stored as regular 
>directory entries, but the names are encrypted. Anyone with permission can 
>list the contents, but without knowing the key he gets gibberish. The names 
>are stored in hex; we could also use base64 or base85, or come up with a 
>cipher that avoids producing nulls and slashes.
>
>
>
>  
>
I'll take a patch;-)

-- 
Hans