Re: [PATCH 3/3] ecryptfs: added ecryptfs_mount_auth_tok_only mount parameter

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Tyler Hicks
Date: Friday, October 8, 2010 - 12:08 pm

On Wed Oct 06, 2010 at 06:31:32PM +0200, Roberto Sassu <roberto.sassu@polito.it> wrote:

Hey Roberto - The commit message tells me what this patch does, but I'm
curious about why you want to do it. Not that it is a bad idea, but I'd
like to understand if it will be a useful feature before adding another
mount option. Each mount option increases testing that must be covered,
although the additional code path here is extremely simple.

An example scenario would be much appreciated.

Why would the user have files encrypted with other keys in the lower
directory? Without any type of encryption policy support in eCryptfs,
I would think that all files in the lower filesystem would be encrypted
only by the keys specified by the ecryptfs*_sig parameters.



--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH 3/3] ecryptfs: added ecryptfs_mount_auth_tok_on ..., Tyler Hicks, (Fri Oct 8, 12:08 pm)