From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 47A0AC4332F for ; Mon, 6 Sep 2021 14:57:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2391460F9E for ; Mon, 6 Sep 2021 14:57:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243716AbhIFO6F (ORCPT ); Mon, 6 Sep 2021 10:58:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39158 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243640AbhIFO6A (ORCPT ); Mon, 6 Sep 2021 10:58:00 -0400 Received: from mail-vk1-xa30.google.com (mail-vk1-xa30.google.com [IPv6:2607:f8b0:4864:20::a30]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 08FCEC061575 for ; Mon, 6 Sep 2021 07:56:56 -0700 (PDT) Received: by mail-vk1-xa30.google.com with SMTP id t19so2285756vkk.2 for ; Mon, 06 Sep 2021 07:56:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=szeredi.hu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+wm+1SxyPhgZ2xyPaqVHOlIIYUpLoXtqsuq+0VC3Sjc=; b=moj6OWG2vw6GntXNWeTQgm7Smvy1QpBa4fBHcAMupAuzUukRol/FdrWgU5z93l3NPQ 6MKcKRVOHIc1gnlY06/SaTKFIeV+7N4mqBXunJXSVgBRCYLv1sIi2A1t7PSoceroEu42 nlrzfwR/cKNVYtbEIrt0+iEauNFt1iHYtCXY0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+wm+1SxyPhgZ2xyPaqVHOlIIYUpLoXtqsuq+0VC3Sjc=; b=LY34o7Hb31+512vgSJqEJHlZxLAU5mfSaMTCMifVQA4yVdCcfGrycHdnsqBGPQJYzw UGMKnETc3JXl39hAn8HnRgz5Z3UPWYiBF4QfjfvdboQCscpjMgh8T6qyQi3kQXAmcJrk uRQ4G9jNcaLs2TjEGtVxDm1hHOUWXFf7IuWQkNFEnvAIwF3Oww8UVvt7LXaXJWzNrv7v Ges9PIyb3YUPgVFeMF7btKzcQ/mAyy/k+q+NhsJHJsKXyLQBchalj1Wm2BOhFR1hwMCh l0cfY6harqdhrkAwzP18I2TSMnlBIkt6Wli9emp5ihhwj3PsThTBDF3fSVUxzeh0YI4t R4+w== X-Gm-Message-State: AOAM533o/8LLqQH1zqljk1tSQcIrlLEiAmAPgWwG6C02V3rzWu2WqR33 /exB/JmLCK/p+ws7TJKNhD7QmrPW6WCgGxKmP+t0Ow== X-Google-Smtp-Source: ABdhPJzqc2z0O4HypL+N5TiFC1yajscDCqIXhB97hRi7jls6qKs/M/pVB7E0LSC2ATi0XpZDADaqMYws03dQ9iRqjxM= X-Received: by 2002:a05:6122:1430:: with SMTP id o16mr5404231vkp.14.1630940215149; Mon, 06 Sep 2021 07:56:55 -0700 (PDT) MIME-Version: 1.0 References: <20210902152228.665959-1-vgoyal@redhat.com> In-Reply-To: From: Miklos Szeredi Date: Mon, 6 Sep 2021 16:56:44 +0200 Message-ID: Subject: Re: [PATCH v3 0/1] Relax restrictions on user.* xattr To: "Dr. David Alan Gilbert" Cc: Andreas Gruenbacher , Vivek Goyal , Alexander Viro , linux-fsdevel , LKML , virtio-fs-list , Daniel J Walsh , Christian Brauner , casey.schaufler@intel.com, LSM , SElinux list , "Theodore Ts'o" , Giuseppe Scrivano , "Fields, Bruce" , Stephen Smalley , Dave Chinner , "Eric W. Biederman" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 6 Sept 2021 at 16:39, Dr. David Alan Gilbert wrote: > IMHO the real problem here is that the user/trusted/system/security > 'namespaces' are arbitrary hacks rather than a proper namespacing > mechanism that allows you to create new (nested) namespaces and associate > permissions with each one. Indeed. This is what Eric Biederman suggested at some point for supporting trusted xattrs within a user namespace: | For trusted xattrs I think it makes sense in principle. The namespace | would probably become something like "trusted.". Theory sounds simple enough. Anyone interested in looking at the details? Thanks, Miklos From mboxrd@z Thu Jan 1 00:00:00 1970 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=szeredi.hu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+wm+1SxyPhgZ2xyPaqVHOlIIYUpLoXtqsuq+0VC3Sjc=; b=moj6OWG2vw6GntXNWeTQgm7Smvy1QpBa4fBHcAMupAuzUukRol/FdrWgU5z93l3NPQ 6MKcKRVOHIc1gnlY06/SaTKFIeV+7N4mqBXunJXSVgBRCYLv1sIi2A1t7PSoceroEu42 nlrzfwR/cKNVYtbEIrt0+iEauNFt1iHYtCXY0= MIME-Version: 1.0 References: <20210902152228.665959-1-vgoyal@redhat.com> In-Reply-To: From: Miklos Szeredi Date: Mon, 6 Sep 2021 16:56:44 +0200 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: Re: [Virtio-fs] [PATCH v3 0/1] Relax restrictions on user.* xattr List-Id: Development discussions about virtio-fs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Dr. David Alan Gilbert" Cc: Giuseppe Scrivano , Theodore Ts'o , Andreas Gruenbacher , SElinux list , Stephen Smalley , Dave Chinner , LKML , virtio-fs-list , casey.schaufler@intel.com, LSM , Alexander Viro , linux-fsdevel , "Fields, Bruce" , Christian Brauner , Vivek Goyal , "Eric W. Biederman" On Mon, 6 Sept 2021 at 16:39, Dr. David Alan Gilbert wrote: > IMHO the real problem here is that the user/trusted/system/security > 'namespaces' are arbitrary hacks rather than a proper namespacing > mechanism that allows you to create new (nested) namespaces and associate > permissions with each one. Indeed. This is what Eric Biederman suggested at some point for supporting trusted xattrs within a user namespace: | For trusted xattrs I think it makes sense in principle. The namespace | would probably become something like "trusted.". Theory sounds simple enough. Anyone interested in looking at the details? Thanks, Miklos