IETF Logo Mail Archive

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

Nico Williams <nico@cryptonector.com> Thu, 25 May 2017 18:22 UTC

Return-Path: <nico@cryptonector.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 4AA01129B95; Thu, 25 May 2017 11:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level:
X-Spam-Status: No, score=-4.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 gRZE2JHzHIVd; Thu, 25 May 2017 11:22:51 -0700 (PDT)
Received: from homiemail-a107.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EE1D124D85; Thu, 25 May 2017 11:22:51 -0700 (PDT)
Received: from homiemail-a107.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a107.g.dreamhost.com (Postfix) with ESMTP id CAAB020051C27; Thu, 25 May 2017 11:22:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=p1eJndX2+dZvm0 bxOLW1f7Qr2a4=; b=WXs7CxnpXpGGrpZegYxXJEqCe4AOUrccdG74Y3Vlf3cp+4 rhjvBx1+1y53sg1yk8hRjB6VX7b6XxjsHMrMHRd6Qu4CfvJTCjs6zRXLcwNkXRxw T2aqizDo/BKhKhhGjXL3AcXJMurBiaRMHhTSyQCl8O3TFw9ooDqQo27ld+oFU=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a107.g.dreamhost.com (Postfix) with ESMTPSA id E2D0020051C23; Thu, 25 May 2017 11:22:49 -0700 (PDT)
Date: Thu, 25 May 2017 13:22:47 -0500
From: Nico Williams <nico@cryptonector.com>
To: Marc Eshel <eshel@us.ibm.com>
Cc: draft-ietf-nfsv4-xattrs@ietf.org, Eric Rescorla <ekr@rtfm.com>, The IESG <iesg@ietf.org>, NFSv4 <nfsv4@ietf.org>, nfsv4-chairs@ietf.org, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Message-ID: <20170525182246.GW10188@localhost>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <OFE1A7E856.598CE2A7-ON8825812B.00586825-8825812B.0058FAF1@notes.na.collabserv.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/s0peublngApZHaf6rsVtcpmxYqc>
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: Thu, 25 May 2017 18:22:52 -0000

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.

v2.23.0 | Report a Bug | By Email