linux-kernel - Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path

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: <20150803230754.GB2342@boyd>
Date:	Mon, 3 Aug 2015 18:07:54 -0500
From:	Tyler Hicks <tyhicks@...onical.com>
To:	Richard Weinberger <richard@....at>
Cc:	ecryptfs@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path

On 2015-08-03 20:31:57, Richard Weinberger wrote:
> Tyler,
> 
> Am 03.08.2015 um 07:27 schrieb Tyler Hicks:
> >> So ecryptfs definitely supports mounting the same lower path multiple times?
> >> What is the benefit of that behavior?
> > 
> > No, it doesn't support that in a way that provides consistency among all
> > of the eCryptfs mounts.
> 
> Okay, then I'd argument to give my patch a try although it is not the solution
> to the problem I've reported. :-)
> If you don't mind I'll resend with a proper changelog.

That patch isn't correct since it assumes that all eCryptfs super blocks
are equal if the lower paths (and, ultimately, the lower inode) are
equal. However, the lower path is only one of many properties of an
eCryptfs superblock. For example, the second mount may have been
configured to use a different file encryption key.

Tyler

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)