linux-kernel - Re: [REVIEW][PATCH] vfs: Lock in place mounts from more privileged users

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: <CALCETrWCxny906McvR9gjn6cqXvO4Mjp3gGPKDnWbYd4ocBmcw@mail.gmail.com>
Date:	Wed, 24 Jul 2013 08:46:45 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Linux Containers <containers@...ts.linux-foundation.org>,
	"Serge E. Hallyn" <serge@...lyn.com>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [REVIEW][PATCH] vfs: Lock in place mounts from more privileged users

On Tue, Jul 23, 2013 at 11:50 PM, Eric W. Biederman
<ebiederm@...ssion.com> wrote:
> Andy Lutomirski <luto@...capital.net> writes:
>> On Tue, Jul 23, 2013 at 11:30 AM, Eric W. Biederman
>> <ebiederm@...ssion.com> wrote:
>>>
>>> When creating a less privileged mount namespace or propogating mounts
>>> from a more privileged to a less privileged mount namespace lock the
>>> submounts so they may not be unmounted individually in the child mount
>>> namespace revealing what is under them.
>>
>> I would propose a different rule: if vfsmount b is mounted on vfsmount
>> a, then to unmount b, you must be ns_capable(CAP_SYS_MOUNT) on either
>> a's namespace or b's namespace.  The idea is that you should be able
>> to see under a mount if you own the parent (because it's yours) or if
>> you own the child (because you, or someone no more privileged than
>> you, put it there).  This may result in a simpler patch and should do
>> much the same thing.
>
> It definitely won't result in a simpler patch as the information you are
> basing the decision on is not available.
>

Ah, I see -- mnt_ns gets changed when the namespace is duplicated.

Acked-by: Andy Lutomirski <luto@...capital.net>

--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/