public inbox for tpm2@lists.linux.dev
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: <Andreas.Fuchs@infineon.com>, <prestwoj@gmail.com>,
	<tpm2@lists.linux.dev>
Subject: Re: TPM2_Sign vs TPM2_RSA_Decrypt
Date: Thu, 16 May 2024 18:20:19 +0300	[thread overview]
Message-ID: <D1B65F2QRSXU.18UDKT6H98GIN@kernel.org> (raw)
In-Reply-To: <4fdcc042a8f74b0e8e5d54a67a1c87e0@infineon.com>

On Thu May 16, 2024 at 5:14 PM EEST,  wrote:
> TPM2_EncryptDecrypt2 is for Symmetric encryption (i.e. AES) only.
>
> I'd still recommend to go for TPM2_Sign().
> Note also that switching may be hard later down the road, since the key usage flags are define during creation.
> So backwards compatibility is nasty here.
>
> Feel free to CC me.
> I'll do what I can.

Great I get that but I'd still start with the existing code because it
was how it was done. I'm strong believer of "change only by stimulus"
and it is rare for feature patch set anyway land in the first round.

BR, Jarkko

  reply	other threads:[~2024-05-16 15:20 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 [this message]
2024-05-17 17:58                   ` Jarkko Sakkinen
2024-05-16 15:18               ` 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=D1B65F2QRSXU.18UDKT6H98GIN@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