public inbox for tpm2@lists.linux.dev
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "James Prestwood" <prestwoj@gmail.com>,
	<Andreas.Fuchs@infineon.com>, <tpm2@lists.linux.dev>
Subject: Re: TPM2_Sign vs TPM2_RSA_Decrypt
Date: Thu, 16 May 2024 18:18:25 +0300	[thread overview]
Message-ID: <D1B63Z0L7EFJ.U9RZFEM3WIDF@kernel.org> (raw)
In-Reply-To: <1107614a-a99d-4997-84f6-e18cc30f5a9a@gmail.com>

On Thu May 16, 2024 at 4:59 PM EEST, James Prestwood wrote:
> On 5/16/24 6:55 AM, Jarkko Sakkinen wrote:
> > On Thu May 16, 2024 at 4:44 PM EEST, James Prestwood wrote:
> >> To be honest I started with encrypt/decrypt and included the signing
> >> operation because it was basically "free" by using tpm2_rsa_decrypt(). I
> >> was not aware of this distinction/difference between that and doing
> >> signing on the TPM itself. I don't think I ever looked into the signing
> >> command on the TPM itself.
> > My personal take: I'd start RSA with the working code and just
> > clean up the parts for the first round. It is tested code and
> > does the job, right? :-)
> It was tested then yes, obviously need to verify that after 4 years :)

Yeah, I gave some nitpicks for you (private) and yeah branch (tpm2_key)
branch has shenigans to call ANS.1 template acquiring function from the
stock RSA code in the kernel :-)

Better to do as little as possible and then we look at what actually
needs to be done.

In addition to Andreas, I'd recommend to first of all CC the patch
set to linux-crypto too in addition to linux-integrity and
keyrings and also Herbert Xu (crypto maintainer).

I know this is some effort to you but isn't it any way worth it
because then the work that you did years ago was not wasted? :-)

BR, Jarkko

      parent reply	other threads:[~2024-05-16 15:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 10:25 TPM2_Sign vs TPM2_RSA_Decrypt Jarkko Sakkinen
2024-05-16 12:01 ` Andreas.Fuchs
2024-05-16 12:51   ` Jarkko Sakkinen
2024-05-16 13:05     ` Andreas.Fuchs
2024-05-16 13:31       ` Jarkko Sakkinen
2024-05-16 13:33         ` Jarkko Sakkinen
2024-05-16 13:44         ` James Prestwood
2024-05-16 13:55           ` Jarkko Sakkinen
2024-05-16 13:59             ` James Prestwood
2024-05-16 14:14               ` Andreas.Fuchs
2024-05-16 15:20                 ` Jarkko Sakkinen
2024-05-17 17:58                   ` Jarkko Sakkinen
2024-05-16 15:18               ` Jarkko Sakkinen [this message]

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=D1B63Z0L7EFJ.U9RZFEM3WIDF@kernel.org \
    --to=jarkko@kernel.org \
    --cc=Andreas.Fuchs@infineon.com \
    --cc=prestwoj@gmail.com \
    --cc=tpm2@lists.linux.dev \
    /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