IETF Logo Mail Archive

Re: [nfsv4] Eric Rescorla's Discuss on draft-ietf-nfsv4-xattrs-05: (with DISCUSS)

bfields@fieldses.org (J. Bruce Fields) Mon, 05 June 2017 18:39 UTC

Return-Path: <bfields@fieldses.org>
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 C3065126DEE; Mon, 5 Jun 2017 11:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 wTAuKdQRoFxW; Mon, 5 Jun 2017 11:39:39 -0700 (PDT)
Received: from fieldses.org (fieldses.org [173.255.197.46]) by ietfa.amsl.com (Postfix) with ESMTP id 15E78129BBE; Mon, 5 Jun 2017 11:39:38 -0700 (PDT)
Received: by fieldses.org (Postfix, from userid 2815) id 1983D1E29; Mon, 5 Jun 2017 14:39:38 -0400 (EDT)
Date: Mon, 05 Jun 2017 14:39:38 -0400
To: Nico Williams <nico@cryptonector.com>
Cc: Marc Eshel <eshel@us.ibm.com>, Eric Rescorla <ekr@rtfm.com>, draft-ietf-nfsv4-xattrs@ietf.org, nfsv4-chairs@ietf.org, NFSv4 <nfsv4@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, The IESG <iesg@ietf.org>
Message-ID: <20170605183938.GA831@fieldses.org>
References: <149559305147.28562.14990485255783585477.idtracker@ietfa.amsl.com> <CAKKJt-cHEoBeP++YP-=FWmVTWkoLWLa5OZ=sDYT7kEBrDvvOiw@mail.gmail.com> <CABcZeBPc9U1D+sSOnz2_3MwVn527ruuqqWoCsZYafx_rLwpyAQ@mail.gmail.com> <CAKKJt-dcjiMFk0NyD-UrBQrtKAZgWaVzcxY67YSDOu0ZVNw9Ng@mail.gmail.com> <CAKKJt-ceK3r8=HXArenmNXpt8bk2MuKbkPL-qoNPZMrHHETfJg@mail.gmail.com> <20170525152957.GV10188@localhost> <OFE1A7E856.598CE2A7-ON8825812B.00586825-8825812B.0058FAF1@notes.na.collabserv.com> <20170525182246.GW10188@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20170525182246.GW10188@localhost>
User-Agent: Mutt/1.5.21 (2010-09-15)
From: bfields@fieldses.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/dFaxmgCnQw55O0tVxVsOcJMP8uA>
Subject: Re: [nfsv4] Eric Rescorla's Discuss on draft-ietf-nfsv4-xattrs-05: (with DISCUSS)
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: Mon, 05 Jun 2017 18:39:41 -0000

On Thu, May 25, 2017 at 01:22:47PM -0500, Nico Williams wrote:
> On Thu, May 25, 2017 at 09:11:53AM -0700, Marc Eshel wrote:
> > We had a lot of discussions in the WG about the security implications and 
> > we decided to stay a way of defining different types of xattr. This is 
> > user only xattr for the applications to use and it should be handled as an 
> > extension to the data in the file without any meaning for the protocol. If 
> > it is not clear enough we can fix the text and add a warning. 
> 
> That's fair, but the point is that the security considerations should be
> very explicit as to this.  MUST/MUST NOT language is called for.

https://tools.ietf.org/html/draft-ietf-nfsv4-xattrs-05#section-5

"Xattr keys and values MUST NOT be interpreted by the NFS clients and
servers"

(and the rest of that paragraph).

--b.

v2.23.0 | Report a Bug | By Email