From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-security-module@vger.kernel.org
Subject: [RFC PATCH] ima: require secure_boot rules in lockdown mode
Date: Thu, 9 Nov 2017 07:53:34 +1100 [thread overview]
Message-ID: <20171109075334.1809f4cc@canb.auug.org.au> (raw)
In-Reply-To: <1510173982.4484.30.camel@linux.vnet.ibm.com>
Hi Mimi,
On Wed, 08 Nov 2017 15:46:22 -0500 Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
>
> [Cc'ing Stephen Rothwell]
>
> On Tue, 2017-10-31 at 14:25 +1100, James Morris wrote:
> > On Mon, 30 Oct 2017, Mimi Zohar wrote:
> >
> > > James is staging the subsystem patches independently of each other, in
> > > case of a similar problem, so that they can be pulled separately.
> > > ?There's a new "next-general" branch.
> >
> > If you send me a pull request, I'm combining branches into next-testing,
> > too, which is pulled into -next.
>
> linux-next already has the IMA patches, which might be confusing.
Not if they are the same *commits* i.e. if the tree/branch that James
merges is the same as the one that I already merge of yours
(git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity#next)
--
Cheers,
Stephen Rothwell
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-08 20:53 UTC|newest]
Thread overview: 17+ 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-30 15:55 ` David Howells
2017-10-30 17:00 ` Mimi Zohar
2017-10-30 17:05 ` David Howells
2017-10-30 17:39 ` Mimi Zohar
2017-10-31 3:25 ` James Morris
2017-11-08 20:46 ` Mimi Zohar
2017-11-08 20:53 ` Stephen Rothwell [this message]
2017-11-08 21:04 ` Mimi Zohar
2017-11-08 23:26 ` Stephen Rothwell
2017-11-09 3:06 ` Mimi Zohar
2017-11-09 13:28 ` James Morris
2017-11-09 13:46 ` Mimi Zohar
2017-11-09 19:17 ` James Morris
2017-11-02 17:11 ` David Howells
2017-11-02 21:30 ` Mimi Zohar
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=20171109075334.1809f4cc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-security-module@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).