From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:38994 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752786AbdACNsG (ORCPT ); Tue, 3 Jan 2017 08:48:06 -0500 Date: Tue, 3 Jan 2017 08:48:06 -0500 From: Vivek Goyal To: Linas Vepstas Cc: Amir Goldstein , Miklos Szeredi , linux-unionfs@vger.kernel.org, linux-fsdevel , Seth Forshee , "Eric W. Biederman" Subject: Re: LXC+overlayfs in unprivileged mode Message-ID: <20170103134806.GA29807@redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sun, Jan 01, 2017 at 02:32:20PM -0600, Linas Vepstas wrote: [..] > It's somehow ironic that the push for user-space mounts and containers > comes from this general fuzzy sensation that they are somehow "safer", > yet the changes to enable this provide a new attack surface for > privilege escalation. Funny world we live in. :-) Happy New Year! Only if unprivileged users want to be able to mount overlayfs. Otherwise, a privileged user can just mount overlayfs on host and bind mount that inside container (this is what docker does). And then you don't have to worry about allowing unprivileged users to be able to allow mounting. Vivek