Received: by 10.223.185.116 with SMTP id b49csp1117160wrg; Wed, 14 Feb 2018 11:55:47 -0800 (PST) X-Google-Smtp-Source: AH8x225fvqvAefkDZusBQ/V9eDqSU4y0qmRd33CaaN4f8euvGKdQ0Si449MsRT7pvwIh/J1JU2HR X-Received: by 10.98.16.157 with SMTP id 29mr207798pfq.60.1518638147534; Wed, 14 Feb 2018 11:55:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518638147; cv=none; d=google.com; s=arc-20160816; b=OueulFbaTt/bTFSggKOBZ9p9EjLu3NrYsmr55iVPYQA6naUArEBC6U/mMwIuX08UcL 87itrZRgeKbcS1gWS7LwaVYlTr4npV3kNNkAAnHrcrjPQeQDhLUouoXdm9ULn2iUyrh2 IzFv1YOeewBe86wTIZxub974wW+VL5aU7FxUx1aBUBtzFNxoP/y7IaREXwQt8NHrv+/j V+crm4vcPAAh2ukywgXZrwN6W2cStYKRw2JkOS5CPuJ73JSlfR5D571E1+qSOZh2w2Kz baHVdQgcV7vPEOEnSvYdoFqkahga5ATQybwN9gm8x4waA07sfo7/Wt/zEqAzTjOHnwuV OqgQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=rnIk+SLDx9uDFJZUNYfxa/4vRIlSAzropD8Kaz0p03E=; b=Hy+ZB/wOgqJ/xTzhB3ws05Je/mxXn4f0NnJO96cwB/mSoZQAHhMv6RqFNEvRfpmdNM Jz/OLcDNacz3d2jm0GtB6pDv5ugXE/wtiwUQevHMP6j/j/AEK2CFyj4ANmxifktgXc9R sb1vZv0FGGsjKdOPICM9keGYgjWGFPgpWG17OQ1BTtM8zEmowo23MQkOCw1tdVrxF7yG o95WGTVPhKSsJU1//GaWZAPugVTeJoz15z+UZWmz4syar3dOuTfsOxT/Ckq+3TFJJtx0 IkKH8Z5+1x95H55awbM5OgSEsAtUMKo4jvSTMls9xJOxCZQC7qR8NkI1EfyPznhQr566 bUew== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 33-v6si8471plo.650.2018.02.14.11.55.32; Wed, 14 Feb 2018 11:55:47 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030499AbeBNOSN (ORCPT + 99 others); Wed, 14 Feb 2018 09:18:13 -0500 Received: from lilium.sigma-star.at ([109.75.188.150]:51704 "EHLO lilium.sigma-star.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030288AbeBNOSM (ORCPT ); Wed, 14 Feb 2018 09:18:12 -0500 Received: from localhost (localhost [127.0.0.1]) by lilium.sigma-star.at (Postfix) with ESMTP id F0F621800005E; Wed, 14 Feb 2018 15:18:10 +0100 (CET) From: Richard Weinberger To: Enrico Weigelt Cc: Aleksa Sarai , Linux Containers , "linux-kernel@vger.kernel.org" Subject: Re: plan9 semantics on Linux - mount namespaces Date: Wed, 14 Feb 2018 15:19:24 +0100 Message-ID: <2050418.Dl5pXkWGsk@blindfold> In-Reply-To: References: <0f058286-a432-379b-f559-f2fe713807ab@metux.net> <2658681.ustYaP9yci@blindfold> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Mittwoch, 14. Februar 2018, 15:03:55 CET schrieb Enrico Weigelt: > On 14.02.2018 13:53, Richard Weinberger wrote: > > It does what you ask it for. > Also see the --setgroups switch.> AFAICT > > --setgroups=deny is the new > default, then your command line should just> work. Maybe your unshare > tool is too old. > Also doesn't help: > > daemon@alphabox:~ unshare -U -r --setgroups=deny > unshare: can't open '/proc/self/setgroups': Permission denied Works here(tm). Can you debug it? Maybe we miss something obvious. > >> What I'd like to achieve is that processes can manipulate their private > >> >> namespace at will and mount other filesystems (primarily 9p and > fuse).>>>> For that, I need to get rid of setuid (and per-file caps) for > these>> private namespaces.> > > > This is exactly why we have the user namespace. > > In the user namespace you can create your own mount namespace and do > > (almost) whatever you want. > > What's the exact relation between user and mnt namespace ? > Why do I need an own user ns for private mnt ns ? (except for the suid > bit, which I wanna get rid of anyways). mount related system calls are root-only. Therefore you need the user namespace to become a root in your own little world. :) Thanks, //richard -- sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria ATU66964118 - FN 374287y