linux-kernel - Re: [PATCH 0/5] eCryptfs: Filename Encryption

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081106202736.GC6688@halcrowt61p.austin.ibm.com>
Date:	Thu, 6 Nov 2008 14:27:36 -0600
From:	Michael Halcrow <mhalcrow@...ibm.com>
To:	Pavel Machek <pavel@...e.cz>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Dustin Kirkland <dustin.kirkland@...il.com>,
	Eric Sandeen <sandeen@...hat.com>,
	Tyler Hicks <tchicks@...ibm.com>,
	David Kleikamp <shaggy@...ibm.com>
Subject: Re: [PATCH 0/5] eCryptfs: Filename Encryption

On Wed, Nov 05, 2008 at 04:57:54PM +0100, Pavel Machek wrote:
> 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?

If the lower filename has the prefix but does not have a valid tag 70
packet following the prefix, then eCryptfs will complain in the syslog
and then pass through the lower filename as-is.

Content of type "application/pgp-signature" skipped