Keyrings Archive mirror
 help / color / mirror / Atom feed
From: Genes Lists <lists@sapience.com>
To: linux-kernel@vger.kernel.org, dhowells@redhat.com,
	dwmw2@infradead.org, keyrings@vger.kernel.org
Subject: Re: Hash sha3-512 vs scripts/sign-file vs openssl
Date: Sun, 5 Nov 2023 17:45:53 -0500	[thread overview]
Message-ID: <e76b6853-95e9-46b4-bc8a-ac10a1be2246@sapience.com> (raw)
In-Reply-To: <be576842-6ad5-43f8-abcf-bd7fa84e235d@sapience.com>

On 11/5/23 16:49, Genes Lists wrote:
> Mainline modules signing supports sha3-xxx.
> 
..
>   At main.c:321:
> - SSL error:2EFFF06F:CMS routines:CRYPTO_internal:ctrl failure: 
> cms/cms_sd.c:269
> 
> openssl version here on arch is 3.1.4 and this may quite possibly be 
..

I confirm that linking sign-file against openssl git head works fine.

So it should be fixed in openssl 3.2

regards,

gene


      reply	other threads:[~2023-11-05 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-05 21:49 Hash sha3-512 vs scripts/sign-file vs openssl Genes Lists
2023-11-05 22:45 ` Genes Lists [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=e76b6853-95e9-46b4-bc8a-ac10a1be2246@sapience.com \
    --to=lists@sapience.com \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).