All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Pierre Abbat <phma@webjockey.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiser4 crypto-compression design
Date: Thu, 27 Mar 2003 19:30:11 +0300	[thread overview]
Message-ID: <3E832713.6050004@namesys.com> (raw)
In-Reply-To: <200303261916.37039.phma@webjockey.net>

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



  reply	other threads:[~2003-03-27 16:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25 19:52 Reiser4 crypto-compression design Edward Shushkin
2003-03-25 20:23 ` Hendrik Visage
2003-03-26 17:03   ` Edward Shushkin
2003-03-26 18:21     ` Hans Reiser
2003-03-26 18:53     ` Hendrik Visage
2003-03-27 16:15       ` Edward Shushkin
2003-03-26 12:30 ` Pierre Abbat
2003-03-26 18:33   ` Hans Reiser
2003-03-26 20:35   ` Hubert Chan
2003-03-26 21:39     ` Hans Reiser
2003-03-27  0:16     ` Pierre Abbat
2003-03-27 16:30       ` Hans Reiser [this message]
2003-03-27 23:34         ` Pierre Abbat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E832713.6050004@namesys.com \
    --to=reiser@namesys.com \
    --cc=phma@webjockey.net \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.