linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Nayna Jain <nayna@linux.ibm.com>,
	linux-integrity@vger.kernel.org, keyrings@vger.kernel.org
Cc: dhowells@redhat.com, jarkko@kernel.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, dimitri.ledkov@canonical.com,
	seth@forshee.me
Subject: Re: [PATCH v8 1/3] certs: export load_certificate_list() to be used outside certs/
Date: Thu, 27 Jan 2022 09:52:47 -0500	[thread overview]
Message-ID: <76e7b1aa85c1ce2d147713306e5996eb55ba3987.camel@linux.ibm.com> (raw)
In-Reply-To: <20220111183647.977037-2-nayna@linux.ibm.com>

Hi Jarkko,

On Tue, 2022-01-11 at 13:36 -0500, Nayna Jain wrote:
> load_certificate_list() parses certificates embedded in the kernel
> image to load them onto the keyring.
> 
> Commit "2565ca7f5ec1 (certs: Move load_system_certificate_list to a common
> function)" made load_certificate_list() a common function in the certs/
> directory. Export load_certificate_list() outside certs/ to be used by
> load_platform_certificate_list() for loading compiled in platform keys
> onto the .platform keyring at boot time. 
> 
> Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
> Signed-off-by: Nayna Jain <nayna@linux.ibm.com>

I think Nayna addressed your concerns.  Did you want to upstream this
patch set or would you prefer I did?

thanks,

Mimi


  reply	other threads:[~2022-01-27 14:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 18:36 [PATCH v8 0/3] integrity: support including firmware ".platform" keys at build time Nayna Jain
2022-01-11 18:36 ` [PATCH v8 1/3] certs: export load_certificate_list() to be used outside certs/ Nayna Jain
2022-01-27 14:52   ` Mimi Zohar [this message]
2022-01-11 18:36 ` [PATCH v8 2/3] integrity: make integrity_keyring_from_id() non-static Nayna Jain
2022-01-11 18:36 ` [PATCH v8 3/3] integrity: support including firmware ".platform" keys at build time Nayna Jain
2022-02-20 23:02 ` [PATCH v8 0/3] " Jarkko Sakkinen
2022-02-21 13:33   ` Nayna
2022-03-02  4:21     ` Jarkko Sakkinen

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=76e7b1aa85c1ce2d147713306e5996eb55ba3987.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=dimitri.ledkov@canonical.com \
    --cc=jarkko@kernel.org \
    --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=nayna@linux.ibm.com \
    --cc=seth@forshee.me \
    /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).