From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: trond.myklebust@hammerspace.com,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: EVM HMAC and FS UUID
Date: Tue, 22 May 2018 12:07:51 -0400 [thread overview]
Message-ID: <20180522160751.GB30724@fieldses.org> (raw)
In-Reply-To: <04B6BFF9-AC1E-4E46-810B-7DDE5ED63345@oracle.com>
On Tue, May 22, 2018 at 08:53:34AM -0700, Chuck Lever wrote:
> Hi-
>
> I'm continuing to look at NFS support for the Linux Integrity
> Measurement Architecture.
>
> When computing an HMAC hash of file attributes, sometimes the
> FS UUID is included. For a client to verify that hash, the
> server will have to expose that UUID somehow.
>
> Is there currently an NFSv4 attribute that carries the FS UUID?
I think the fsid is as close as you get.
Do you need to calculate hashes in exactly the way the server does? If
you're assuming a "dumb server" that just stores signatures without
interpreting them, then maybe not?
--b.
next prev parent reply other threads:[~2018-05-22 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 15:53 EVM HMAC and FS UUID Chuck Lever
2018-05-22 16:07 ` Bruce Fields [this message]
2018-05-22 16:17 ` Chuck Lever
2018-05-22 20:17 ` Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180522160751.GB30724@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox