From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-crypto@vger.kernel.org,
linux-security-module@vger.kernel.org, dhowells@redhat.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
jejb@linux.ibm.com, zohar@linux.ibm.com, jmorris@namei.org,
serge@hallyn.com, casey@schaufler-ca.com,
ard.biesheuvel@linaro.org, daniel.thompson@linaro.org,
linux-kernel@vger.kernel.org, tee-dev@lists.linaro.org
Subject: Re: [RFC/RFT v2 1/2] KEYS: trusted: create trusted keys subsystem
Date: Thu, 01 Aug 2019 17:24:15 +0000 [thread overview]
Message-ID: <20190801172310.cldcftfdoh5vyfjg@linux.intel.com> (raw)
In-Reply-To: <1563449086-13183-2-git-send-email-sumit.garg@linaro.org>
On Thu, Jul 18, 2019 at 04:54:45PM +0530, Sumit Garg wrote:
> Move existing code to trusted keys subsystem. Also, rename files with
> "tpm" as suffix which provides the underlying implementation.
>
> Suggested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
What about TPM2 trusted keys code?
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-crypto@vger.kernel.org,
linux-security-module@vger.kernel.org, dhowells@redhat.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
jejb@linux.ibm.com, zohar@linux.ibm.com, jmorris@namei.org,
serge@hallyn.com, casey@schaufler-ca.com,
ard.biesheuvel@linaro.org, daniel.thompson@linaro.org,
linux-kernel@vger.kernel.org, tee-dev@lists.linaro.org
Subject: Re: [RFC/RFT v2 1/2] KEYS: trusted: create trusted keys subsystem
Date: Thu, 1 Aug 2019 20:24:15 +0300 [thread overview]
Message-ID: <20190801172310.cldcftfdoh5vyfjg@linux.intel.com> (raw)
In-Reply-To: <1563449086-13183-2-git-send-email-sumit.garg@linaro.org>
On Thu, Jul 18, 2019 at 04:54:45PM +0530, Sumit Garg wrote:
> Move existing code to trusted keys subsystem. Also, rename files with
> "tpm" as suffix which provides the underlying implementation.
>
> Suggested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
What about TPM2 trusted keys code?
/Jarkko
next prev parent reply other threads:[~2019-08-01 17:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 11:24 [RFC/RFT v2 0/2] KEYS: trusted: Add generic trusted keys framework Sumit Garg
2019-07-18 11:36 ` Sumit Garg
2019-07-18 11:24 ` [RFC/RFT v2 1/2] KEYS: trusted: create trusted keys subsystem Sumit Garg
2019-07-18 11:36 ` Sumit Garg
2019-08-01 17:24 ` Jarkko Sakkinen [this message]
2019-08-01 17:24 ` Jarkko Sakkinen
2019-08-02 5:50 ` Sumit Garg
2019-08-02 5:50 ` Sumit Garg
2019-08-02 19:38 ` Jarkko Sakkinen
2019-08-02 19:38 ` Jarkko Sakkinen
2019-08-05 5:02 ` Sumit Garg
2019-08-05 5:14 ` Sumit Garg
2019-08-05 20:59 ` Jarkko Sakkinen
2019-08-05 20:59 ` Jarkko Sakkinen
2019-07-18 11:24 ` [RFC/RFT v2 2/2] KEYS: trusted: Add generic trusted keys framework Sumit Garg
2019-07-18 11:36 ` Sumit Garg
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=20190801172310.cldcftfdoh5vyfjg@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=casey@schaufler-ca.com \
--cc=daniel.thompson@linaro.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jejb@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=sumit.garg@linaro.org \
--cc=tee-dev@lists.linaro.org \
--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 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.