From: Chuck Lever <chuck.lever@oracle.com>
To: linux-integrity@vger.kernel.org
Subject: LPC 2018
Date: Tue, 9 Oct 2018 11:58:18 -0400 [thread overview]
Message-ID: <9808035C-5AE5-4594-BDBF-A51544231608@oracle.com> (raw)
I'm planning to attend LPC next month. I'm interested in discussing
IMA on distributed file systems in particular with anyone here who
might also attend. I expect it would be a narrow topic, so a birds
of a feather is probably appropriate, but hallway track could work
too.
I especially would like to discuss the on-disk format of IMA
metadata, and how the IMA module behaves when it encounters metadata
it does not recognize (or how you do on-disk format versioning).
I'm still working on an Internet Draft that specifies how to enable
IMA on NFS files. The biggest challenge has been the lack of IMA
spec. The current revision of the Draft describes the requirements
in generic terms, and cites the IMA wiki/white paper only as an
Informative reference. I believe this will be adequate.
I've also dropped EVM support for now. Two concerns:
- NFS does not expose some file attributes that EVM protects
- The format of some file attributes might not be the same on all
client OSes.
More to talk about in person, I hope.
https://datatracker.ietf.org/doc/draft-ietf-nfsv4-integrity-measurement/
--
Chuck Lever
next reply other threads:[~2018-10-09 23:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 15:58 Chuck Lever [this message]
2018-10-10 1:05 ` LPC 2018 Monty Wiseman
2018-10-11 15:48 ` Serge E. Hallyn
2018-10-11 19:49 ` Monty Wiseman
2018-10-11 22:18 ` James Bottomley
2018-10-15 13:53 ` Jarkko Sakkinen
2018-10-15 18:48 ` Matthew Garrett
2018-10-15 21:35 ` James Morris
2018-10-15 22:28 ` James Bottomley
2018-10-15 22:46 ` James Morris
2018-10-16 11:56 ` Mimi Zohar
2018-10-16 11:56 ` Mimi Zohar
2018-10-16 15:34 ` James Bottomley
2018-10-16 19:09 ` Mimi Zohar
2018-10-16 19:13 ` James Bottomley
2018-10-18 0:05 ` Jarkko Sakkinen
2018-10-20 18:23 ` Nayna Jain
2018-10-23 13:16 ` Jarkko Sakkinen
2018-10-23 13:31 ` James Bottomley
2018-10-23 13:36 ` LSS-EU BoF(s) (renamed from LPC 2018) Mimi Zohar
2018-10-24 14:42 ` Monty Wiseman
2018-10-24 15:55 ` Aw: " Peter Huewe
2018-10-24 16:25 ` Mimi Zohar
2018-10-24 16:28 ` James Bottomley
2018-10-25 7:14 ` Jarkko Sakkinen
2018-10-17 23:49 ` LPC 2018 Jarkko Sakkinen
2018-10-23 13:39 ` David Howells
2018-10-23 13:47 ` James Bottomley
2018-10-23 13:56 ` David Howells
2018-10-24 8:45 ` Jarkko Sakkinen
2018-10-24 8:59 ` James Bottomley
2018-10-24 9:17 ` Monty Wiseman
2018-10-24 15:27 ` Jarkko Sakkinen
2018-10-24 15:54 ` Roberto Sassu
2018-10-24 16:05 ` James Bottomley
2018-10-17 23:47 ` Jarkko Sakkinen
2018-10-17 23:48 ` James Bottomley
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=9808035C-5AE5-4594-BDBF-A51544231608@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-integrity@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.