Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753824AbYKFHUs (ORCPT ); Thu, 6 Nov 2008 02:20:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752690AbYKFHUk (ORCPT ); Thu, 6 Nov 2008 02:20:40 -0500 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:39823 "EHLO UNKNOWN" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752244AbYKFHUk (ORCPT ); Thu, 6 Nov 2008 02:20:40 -0500 Date: Wed, 5 Nov 2008 16:57:54 +0100 From: Pavel Machek To: Michael Halcrow Cc: Andrew Morton , LKML , Dustin Kirkland , Eric Sandeen , Tyler Hicks , David Kleikamp Subject: Re: [PATCH 0/5] eCryptfs: Filename Encryption Message-ID: <20081105155754.GA1759@ucw.cz> References: <20081104213754.GC6675@halcrowt61p.austin.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081104213754.GC6675@halcrowt61p.austin.ibm.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 874 Lines: 19 On Tue 2008-11-04 15:37:54, Michael Halcrow wrote: > This patchset implements filename encryption via a passphrase-derived > mount-wide Filename Encryption Key (FNEK) specified as a mount > parameter. Each encrypted filename has a fixed prefix indicating that > eCryptfs should try to decrypt the filename. When eCryptfs > encounters That is 'interesting'. What happens if normal filename has that prefix? Should some out-of-band method be used to tell normal and encrypted filenames apart? -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/