From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Morris Subject: Re: eCryptfs Design Document Date: Fri, 24 Mar 2006 18:12:46 -0500 (EST) Message-ID: References: <20060324222517.GA13688@us.ibm.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Andrew Morton , phillip@hellewell.homeip.net, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, viro@ftp.linux.org.uk, mike@halcrow.us, mcthomps@us.ibm.com, yoder1@us.ibm.com, toml@us.ibm.com, emilyr@us.ibm.com, daw@cs.berkeley.edu Return-path: Received: from mail7.sea5.speakeasy.net ([69.17.117.9]:33926 "EHLO mail7.sea5.speakeasy.net") by vger.kernel.org with ESMTP id S964816AbWCXXMt (ORCPT ); Fri, 24 Mar 2006 18:12:49 -0500 To: Michael Halcrow In-Reply-To: <20060324222517.GA13688@us.ibm.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, 24 Mar 2006, Michael Halcrow wrote: > initialization vector by taking the MD5 sum of the file encryption > key; the root IV is the first N bytes of that MD5 sum, where N is the > number of bytes constituting an initialization vector for the cipher > being used for the file (it is worth noting that known plaintext > attacks against the MD5 hash algorithm do not affect the security of > eCryptfs, since eCryptfs only hashes secret values). What about other attacks on MD5? Hard coding it into the system makes me nervous, what about making this selectable? > By default, eCryptfs selects AES-128. Later versions of eCryptfs will > allow the user to select the cipher and key length. Also, what about making the encryption mode selectable, to at least allow for like LRW support in addition to CBC? - James -- James Morris