From: James Morris <james.l.morris@oracle.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
David Howells <dhowells@redhat.com>,
linux-integrity <linux-integrity@vger.kernel.org>,
Matthew Garrett <mjg59@google.com>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [RFC PATCH] ima: require secure_boot rules in lockdown mode
Date: Fri, 10 Nov 2017 06:17:49 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1711100617360.5638@localhost> (raw)
In-Reply-To: <1510235213.4484.165.camel@linux.vnet.ibm.com>
On Thu, 9 Nov 2017, Mimi Zohar wrote:
> Thank you for the clarification (and patience). There are a lot of
> interactions between the integrity subsystem and the other security
> subsystems, especially the TPM. Assuming it is acceptable, as you
> said, I'd really prefer continuing to have the integrity subsystem
> merged via the security tree.
That's fine, whatever works for you.
--
James Morris
<james.l.morris@oracle.com>
WARNING: multiple messages have this Message-ID (diff)
From: james.l.morris@oracle.com (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [RFC PATCH] ima: require secure_boot rules in lockdown mode
Date: Fri, 10 Nov 2017 06:17:49 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1711100617360.5638@localhost> (raw)
In-Reply-To: <1510235213.4484.165.camel@linux.vnet.ibm.com>
On Thu, 9 Nov 2017, Mimi Zohar wrote:
> Thank you for the clarification (and patience). ?There are a lot of
> interactions between the integrity subsystem and the other security
> subsystems, especially the TPM. ?Assuming it is acceptable, as you
> said, I'd really prefer continuing to have the integrity subsystem
> merged via the security tree.
That's fine, whatever works for you.
--
James Morris
<james.l.morris@oracle.com>
next prev parent reply other threads:[~2017-11-09 19:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 15:59 [RFC PATCH] ima: require secure_boot rules in lockdown mode Mimi Zohar
2017-10-23 15:59 ` Mimi Zohar
2017-10-30 15:55 ` David Howells
2017-10-30 15:55 ` David Howells
2017-10-30 17:00 ` Mimi Zohar
2017-10-30 17:00 ` Mimi Zohar
2017-10-30 17:05 ` David Howells
2017-10-30 17:05 ` David Howells
2017-10-30 17:39 ` Mimi Zohar
2017-10-30 17:39 ` Mimi Zohar
2017-10-31 3:25 ` James Morris
2017-10-31 3:25 ` James Morris
2017-11-08 20:46 ` Mimi Zohar
2017-11-08 20:46 ` Mimi Zohar
2017-11-08 20:53 ` Stephen Rothwell
2017-11-08 20:53 ` Stephen Rothwell
2017-11-08 21:04 ` Mimi Zohar
2017-11-08 21:04 ` Mimi Zohar
2017-11-08 23:26 ` Stephen Rothwell
2017-11-08 23:26 ` Stephen Rothwell
2017-11-09 3:06 ` Mimi Zohar
2017-11-09 3:06 ` Mimi Zohar
2017-11-09 13:28 ` James Morris
2017-11-09 13:28 ` James Morris
2017-11-09 13:46 ` Mimi Zohar
2017-11-09 13:46 ` Mimi Zohar
2017-11-09 19:17 ` James Morris [this message]
2017-11-09 19:17 ` James Morris
2017-11-02 17:11 ` David Howells
2017-11-02 17:11 ` David Howells
2017-11-02 21:30 ` Mimi Zohar
2017-11-02 21:30 ` Mimi Zohar
2017-11-02 21:43 ` David Howells
2017-11-02 21:43 ` David Howells
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=alpine.LFD.2.20.1711100617360.5638@localhost \
--to=james.l.morris@oracle.com \
--cc=dhowells@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjg59@google.com \
--cc=sfr@canb.auug.org.au \
--cc=zohar@linux.vnet.ibm.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 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.