Re: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-integrity-measurement-03.txt
Chuck Lever <chuck.lever@oracle.com> Fri, 09 November 2018 15:27 UTC
Return-Path: <chuck.lever@oracle.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 A1EB112D4E9 for <nfsv4@ietfa.amsl.com>; Fri, 9 Nov 2018 07:27:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.77
X-Spam-Level:
X-Spam-Status: No, score=-4.77 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 V2mpCy1reEIS for <nfsv4@ietfa.amsl.com>; Fri, 9 Nov 2018 07:27:34 -0800 (PST)
Received: from userp2130.oracle.com (userp2130.oracle.com [156.151.31.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 312281277C8 for <nfsv4@ietf.org>; Fri, 9 Nov 2018 07:27:34 -0800 (PST)
Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id wA9FOLWJ036684; Fri, 9 Nov 2018 15:27:32 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=corp-2018-07-02; bh=eFCvq14v0QwoQo5gPQHZjhgr8TAjVo8Ko69wET9FKNA=; b=iKLEsy/lpt1tbW9OF/12CBFsC2WhpkjE1WQfLD/1qagzlqxcDuVcRVpZ+YHRwcdzIe/3 iwrHRth0vMRZw5gLNDB7Lqg/53gQ4NnAIItuTEfjLHQXeYkLuJqQ5rLUGHEo3kZkW2HY K/PHtnv5aLcBeXozpG/wn1/v5q3GazBywePymQrCdYrU4FeNGFkEvmFdPTYJOwCdMgjk qagn6nFoIE/mq+zz5+OJm5fCySH8D7GrZcSijSWYlXySfYQZfwpIBlL7796ViWMo34MK oqCFbHMZhxXL+ogo9ahxLpn6n1GgP1EG5x0aKsjLJl23GdX3whKTB+jM583sdfnswdog lw==
Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp2130.oracle.com with ESMTP id 2nh33ufng4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 09 Nov 2018 15:27:32 +0000
Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by userv0021.oracle.com (8.14.4/8.14.4) with ESMTP id wA9FRWKA005894 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 9 Nov 2018 15:27:32 GMT
Received: from abhmp0004.oracle.com (abhmp0004.oracle.com [141.146.116.10]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id wA9FRVPr004666; Fri, 9 Nov 2018 15:27:31 GMT
Received: from anon-dhcp-171.1015granger.net (/68.61.232.219) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 09 Nov 2018 07:27:31 -0800
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <CADaq8jf-G30UrgdaG9QcAVPXbtpNpW5mteJMkq5c7ZxPvMaCiQ@mail.gmail.com>
Date: Fri, 09 Nov 2018 10:27:30 -0500
Cc: NFSv4 <nfsv4@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD6828A8-D402-4143-9D52-B34B919E980B@oracle.com>
References: <154160412218.26446.11676556173331817093@ietfa.amsl.com> <74E10D08-6181-49C8-B994-6554C72C4B7D@oracle.com> <BBC9F2E1-4E81-4FE4-99D0-A0B23F33AAD4@netapp.com> <D1E8642B-9A07-4812-82E0-982EDC6EF73E@oracle.com> <578769FE-6C12-4003-A579-7FB461D99A8A@netapp.com> <32BFC3DE-BF20-4A3B-88AC-FAF2C19F714D@oracle.com> <CCC8A8EA-7D8D-440F-B29C-1D3577FC104D@netapp.com> <CDC6A311-4076-405B-AE4C-26A0BC8CE685@oracle.com> <CADaq8jf-G30UrgdaG9QcAVPXbtpNpW5mteJMkq5c7ZxPvMaCiQ@mail.gmail.com>
To: David Noveck <davenoveck@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9071 signatures=668683
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1811090141
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/A48W_d9culZUzzTtqRqWFwMYDKQ>
Subject: Re: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-integrity-measurement-03.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 09 Nov 2018 15:27:35 -0000
Hi Dave- > On Nov 9, 2018, at 5:52 AM, David Noveck <davenoveck@gmail.com> wrote: > > > I do want to have multiple FPI > > blobs per file. > > If so, then this desire could be accommodated more simply than by > allowing each such blob type (fpv_type) to be invidually settable > and retrievable as is suggested in -03. The existing NFSv4 attribute > model would need substantial change to accommodate that. Modifying one at a time doesn't seem impractical, but getting all of them at once would eliminate the need for enumeration. > I think the best way to provide for the possibility of multiple blobs would > be to make the provenace attribute an array of blobs. I think the > following would work but I might have messed up the typdef syntax. > > typedef file_prov4 fattr4_file_provenance[]; The problem with this design is it makes it impossible for the client to predict how large its RPC Reply buffer needs to be. > Those who sign content will need to generate all the blobs they want > to support. I don't see why setting each blob needs to a separate operation. Because they might be set at different points in a file's lifetime by different tools. > Assesors, could get the entire blob set and fairly easily find the blob(s) they want to access. > > > IMA has one for file content, and another one > > for file attributes (the EVM blob). Both can exist at the same > > time. > > OK. > > > I'm specifying only the IMA blob for NFS at this time, as > > explained in a prior email, > > As I understood it, wou were not actually specifying it but were > simply directing people to a description. I can't recall the details, but > I recall some complexity about whether that description was actually > a specfication. What I meant was, I'm requesting from IANA just the IMA container. The EVM container will wait for another document. > > but you should assume that more blobs > > will be coming in the future. > > They might and implemeters will make their own decisions about how much space to allocate to store potenial blobs. -- Chuck Lever
- [nfsv4] I-D Action: draft-ietf-nfsv4-integrity-me… internet-drafts
- [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-integri… Chuck Lever
- Re: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-int… Everhart, Craig
- Re: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-int… Chuck Lever
- Re: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-int… Everhart, Craig
- Re: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-int… Chuck Lever
- Re: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-int… Everhart, Craig
- Re: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-int… Chuck Lever
- Re: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-int… David Noveck
- Re: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-int… Chuck Lever
- Re: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-int… Benjamin Kaduk
- Re: [nfsv4] I-D Action: draft-ietf-nfsv4-integrit… Chuck Lever
- Re: [nfsv4] I-D Action: draft-ietf-nfsv4-integrit… Everhart, Craig
- Re: [nfsv4] I-D Action: draft-ietf-nfsv4-integrit… Benjamin Kaduk
- Re: [nfsv4] I-D Action: draft-ietf-nfsv4-integrit… Chuck Lever