IETF Logo Mail Archive

Re: [nfsv4] New Version Notification for draft-cel-nfsv4-linux-seclabel-xtensions-00.txt

Tom Haynes <loghyr@gmail.com> Thu, 03 May 2018 15:42 UTC

Return-Path: <loghyr@gmail.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E1B12E8D0 for <nfsv4@ietfa.amsl.com>; Thu, 3 May 2018 08:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OmP9sFSLZVeS for <nfsv4@ietfa.amsl.com>; Thu, 3 May 2018 08:42:46 -0700 (PDT)
Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A1E8124C27 for <nfsv4@ietf.org>; Thu, 3 May 2018 08:42:46 -0700 (PDT)
Received: by mail-pg0-x231.google.com with SMTP id z129-v6so9237982pgz.3 for <nfsv4@ietf.org>; Thu, 03 May 2018 08:42:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=lCBZWIVhbyQhbY86qFqBBZagtFT7GEH4np5C3D+C/5I=; b=Al61UVX2JWRQIROohTy3RKI15cBCq7cBe1Ob8FTCE5L/7sMGOPszjtKu3CYkv2CPF0 PQzuV+BQ8zR/SEw8KESuEPg4a/0/7o7WAceyJCNG4lpyyXwqX6zw2qXxEIKNX7FM4Yef X1Iad9rXN7RI0vZAReeH+gToJE+PdxIDBClrNa55lkYMLtQda7pUrjm/lM/UfoGWJtFi Ao47CZ73JSykSY+xNWLfgHNerWrhPl54oa7G6oAlBQIq0U7Ihkg2n43UNUcV7UShfN+q zL1o7CaIgGtfwHWlFsugxOxQXl7esACUx1gmlhshx1nttAwby4uL37Doo9LQl0Jwkdcf vOoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=lCBZWIVhbyQhbY86qFqBBZagtFT7GEH4np5C3D+C/5I=; b=ODFnd7+1yD5VcJDag6psBvnOyFHYg+KGn01uO1OFoPFGxsT0bsXqEvp81Cfsj/gmXC FUsfY0BPwkxNCLSN7iudKS8zT3QzjRdSWfHrKmDHRAA/IbSlUTh9mGbP4NbEjiWNxL+P SB8aX/8MjCgVidhiiq0PYdErV7RTbpkRdKfRcl2kapDNQen+5AkmPVmSiVadpLxEbM08 KWm26s/NwmQ4q3V2h09F0rufe621Yvd779CzvWfAoKRUjFTEBxpoGrN/xuxqI60/cQWj saRFvtnAJyY7MfQ8JGxOQnBZWEQ0gNUmi08n5m0UikHj1JBnSJSk61f7/BJSi9akNnvq 3VEg==
X-Gm-Message-State: ALQs6tAGWvbdeNTOjpfxph9ZUhZb/yjodno50OfkX4DBB38jqUOyc8tE HAmcDaZt/3bOM1za8InUR5w=
X-Google-Smtp-Source: AB8JxZoWSt32iZY5mNZ/mQZqrtXC/gzIcQEi+7r6kCFUgSzxA71Atv+DFL7S0D7AGZ6F5yNH5aj1CA==
X-Received: by 2002:a17:902:1665:: with SMTP id g92-v6mr24731265plg.195.1525362165555; Thu, 03 May 2018 08:42:45 -0700 (PDT)
Received: from kinslayer.corp.primarydata.com (63-157-6-18.dia.static.qwest.net. [63.157.6.18]) by smtp.gmail.com with ESMTPSA id 81sm28046909pfl.92.2018.05.03.08.42.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 May 2018 08:42:44 -0700 (PDT)
From: Tom Haynes <loghyr@gmail.com>
Message-Id: <255272D7-E755-491D-B2CC-5167ABA4C70B@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DA725641-1334-4812-BA93-D3679DC6C074"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Thu, 03 May 2018 08:42:43 -0700
In-Reply-To: <D74605A3-59EE-4237-A270-2CBDD3C7F2D3@oracle.com>
Cc: NFSv4 <nfsv4@ietf.org>
To: Chuck Lever <chuck.lever@oracle.com>
References: <152337099624.13448.11040477333954216664.idtracker@ietfa.amsl.com> <FB6B8D57-CEF6-46E1-97C7-E43C7E49752F@oracle.com> <2CBB38A6-45FF-46A4-96A5-5D1B431E1365@gmail.com> <106AF901BBB25B4082BCE4FEC2F79D440627CED6@ORSMSX108.amr.corp.intel.com> <C388AE74-D240-4CFE-92A3-D0D6B0D31077@oracle.com> <106AF901BBB25B4082BCE4FEC2F79D440627CF0A@ORSMSX108.amr.corp.intel.com> <7898FB59-A717-47E4-AF9B-38720EF40E56@oracle.com> <AEEFCC10-2709-4F03-9C9B-49580D518B46@gmail.com> <D74605A3-59EE-4237-A270-2CBDD3C7F2D3@oracle.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/lHXnYqmp2yLluxdUeI2hKbxYTrA>
Subject: Re: [nfsv4] New Version Notification for draft-cel-nfsv4-linux-seclabel-xtensions-00.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 May 2018 15:42:48 -0000


> On May 3, 2018, at 6:49 AM, Chuck Lever <chuck.lever@oracle.com> wrote:
> 
> 
> 
>> On May 2, 2018, at 8:12 PM, Tom Haynes <loghyr@gmail.com <mailto:loghyr@gmail.com>> wrote:
>> 
>> Hey Chuck,
>> 
>> For some reason I thought you were describing what Linux was doing, not something new...
>> 
>> But yeah, David is right, only one LFS is going to work.
>> 
>> I’ll have to check if xattrs allows for system atttrs, but if it does, why can’t you use them?
> 
> Hi Tom-
> 
> NFSv4 xattrs expose only the user namespace. xattrs in the security.yada namespace
> are not exposed to NFS clients, for example.
> 
> Initially we were thinking of using NFSv4 security labels only for experimentation,
> but there didn't seem to be any reason not to use them for the long-term solution.
> Since it now appears that there can't be a separate label for security.ima and
> security.evm, that makes it challenging to use security labels even for
> experimentation.
> 

No, they are not challenging to use for experimentation if you are using LNFS as designed.

I.e., someone can go in and implement a new Label Format Specifier and use 128 - 255.

BTW, it is also the case that you could not use LFS values of 1, 2, and 3 as described in RFC7569.
The allowed new values start at 260.

v2.23.0 | Report a Bug | By Email