public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: Kamlesh Kumar <kamlesh0hrs@gmail.com>
To: stefanb@linux.ibm.com
Cc: linux-integrity@vger.kernel.org, Kamlesh Kumar <kam@juniper.net>
Subject: Re: [PATCH v3 0/4] Add support for ML-DSA signature for EVM and IMA
Date: Mon,  4 May 2026 16:32:54 +0530	[thread overview]
Message-ID: <20260504110254.88568-1-kam@juniper.net> (raw)
In-Reply-To: <20260416154039.1648083-1-stefanb@linux.ibm.com>

On 4/16/26 11:40 AM, Stefan Berger wrote:

> Based on IMA sigv3 type of signatures, add support for ML-DSA signature
> for EVM and IMA. Use the existing ML-DSA hashless signing mode (pure mode).
> 
>    Stefan
> 
> v3:
>   - new patches 1/4 and 2/4
>   - addressed Mimi's comments on v2
> 
> v2:
>   - Dropped 1/3
>   - Using "none" as hash_algo in 2/2
> 
> Stefan Berger (4):
>   integrity: Check for NULL returned by asymmetric_key_public_key
>   integrity: Check that algo parameter is within valid range
>   integrity: Refactor asymmetric_verify for reusability
>   integrity: Add support for sigv3 verification using ML-DSA keys
> 
>  security/integrity/digsig_asymmetric.c | 152 +++++++++++++++++++++----
>  1 file changed, 131 insertions(+), 21 deletions(-)
> 
> 
> base-commit: 82bbd447199ff1441031d2eaf9afe041550cf525
> -- 
> 2.53.0
> 

Hi Stefan,

I have tested this patch series on x86_64 and IMA signature v3 appraisal
works correctly with ML-DSA keys and appraise_type=sigv3. Signature v3
works with appraise_type=imasig also and I think it is intentional for
backward compatibility of ima policies.

Tested-by: Kamlesh Kumar <kam@juniper.net>

      parent reply	other threads:[~2026-05-04 11:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16 15:40 [PATCH v3 0/4] Add support for ML-DSA signature for EVM and IMA Stefan Berger
2026-04-16 15:40 ` [PATCH v3 1/4] integrity: Check for NULL returned by asymmetric_key_public_key Stefan Berger
2026-04-16 15:40 ` [PATCH v3 2/4] integrity: Check that algo parameter is within valid range Stefan Berger
2026-04-16 15:40 ` [PATCH v3 3/4] integrity: Refactor asymmetric_verify for reusability Stefan Berger
2026-04-16 15:40 ` [PATCH v3 4/4] integrity: Add support for sigv3 verification using ML-DSA keys Stefan Berger
2026-05-04 11:02 ` Kamlesh Kumar [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=20260504110254.88568-1-kam@juniper.net \
    --to=kamlesh0hrs@gmail.com \
    --cc=kam@juniper.net \
    --cc=linux-integrity@vger.kernel.org \
    --cc=stefanb@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