From: Jarkko Sakkinen <jarkko@kernel.org>
To: Nayna <nayna@linux.vnet.ibm.com>
Cc: Nageswara Sastry <rnsastry@linux.ibm.com>,
Nayna Jain <nayna@linux.ibm.com>,
linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
dhowells@redhat.com, zohar@linux.ibm.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, dimitri.ledkov@canonical.com,
seth@forshee.me, Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH v11 0/4] integrity: support including firmware ".platform" keys at build time
Date: Sun, 20 Mar 2022 23:31:19 +0200 [thread overview]
Message-ID: <YjedJxNNv8KifAKd@kernel.org> (raw)
In-Reply-To: <57d7034a-fb5c-444e-a709-4f993459688e@linux.vnet.ibm.com>
On Fri, Mar 18, 2022 at 05:25:07PM -0400, Nayna wrote:
>
> On 3/17/22 03:38, Jarkko Sakkinen wrote:
> > On Fri, Mar 11, 2022 at 04:03:12PM -0500, Nayna wrote:
> > > On 3/11/22 11:42, Jarkko Sakkinen wrote:
> > > > ".platform" keyring.
> > > > > > Changelog:
> > > > > > v11:
> > > > > > * Added a new patch to conditionally build extract-cert if
> > > > > > PLATFORM_KEYRING is enabled.
> > > > > >
> > > > > Tested the following four patches with and with out setting
> > > > > CONFIG_INTEGRITY_PLATFORM_KEYS
> > > > >
> > > > > Tested-by: Nageswara R Sastry <rnsastry@linux.ibm.com>
> > > > OK, I added it:
> > > >
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git
> > > Thanks Jarkko. Masahiro Yamada would prefer to revert the original commit
> > > 340a02535ee785c64c62a9c45706597a0139e972 i.e. move extract-cert back to the
> > > scripts/ directory.
> > >
> > > I am just posting v12 which includes Masahiro feedback. Nageswara has
> > > already tested v12 version as well.
> > >
> > > I am fine either way 1.) Adding v11 and then separately handling of
> > > reverting of the commit or 2.) Adding v12 version which includes the revert.
> > > I leave the decision on you as to which one to upstream.
> > >
> > > Thanks & Regards,
> > >
> > > - Nayna
> > >
> > I already sent PR for v5.18. Too many late changes to include this, which
> > means that v12 is the way to go.
>
> Assuming v12 looks good, could you please queue it now ?
>
> Thanks & Regards,
>
> - Nayna
>
Unfortunately, I've already sent my v5.18 PR over a week ago. I can put it
to my queue but I think it is lacking some of the tested by tags, doesn't
it?
BR, Jarkko
next prev parent reply other threads:[~2022-03-20 21:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 21:44 [PATCH v11 0/4] integrity: support including firmware ".platform" keys at build time Nayna Jain
2022-03-10 21:44 ` [PATCH v11 1/4] certs: export load_certificate_list() to be used outside certs/ Nayna Jain
2022-03-10 21:44 ` [PATCH v11 2/4] integrity: make integrity_keyring_from_id() non-static Nayna Jain
2022-03-10 21:44 ` [PATCH v11 3/4] certs: conditionally build extract-cert if platform keyring is enabled Nayna Jain
2022-03-11 4:34 ` Masahiro Yamada
2022-03-10 21:44 ` [PATCH v11 4/4] integrity: support including firmware ".platform" keys at build time Nayna Jain
2022-03-11 4:41 ` [PATCH v11 0/4] " Nageswara Sastry
2022-03-11 16:42 ` Jarkko Sakkinen
2022-03-11 21:03 ` Nayna
2022-03-17 7:38 ` Jarkko Sakkinen
2022-03-18 21:25 ` Nayna
2022-03-20 21:31 ` Jarkko Sakkinen [this message]
2022-03-11 16:39 ` Jarkko Sakkinen
2022-03-14 12:53 ` Mimi Zohar
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=YjedJxNNv8KifAKd@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=dimitri.ledkov@canonical.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nayna@linux.ibm.com \
--cc=nayna@linux.vnet.ibm.com \
--cc=rnsastry@linux.ibm.com \
--cc=seth@forshee.me \
--cc=zohar@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox