From: "Jarkko Sakkinen" <jarkko.sakkinen@iki.fi>
To: "Neal Gompa" <neal@gompa.dev>,
"David Howells" <dhowells@redhat.com>, <dwmw2@infradead.org>,
<zxu@redhat.com>, <keyrings@vger.kernel.org>,
"Jan Stancek" <jstancek@redhat.com>
Cc: <linux-kernel@vger.kernel.org>,
"Asahi Linux" <asahi@lists.linux.dev>,
"Hector Martin" <marcan@marcan.st>, "Janne Grunau" <j@jannau.net>,
"Jarkko Sakkinen" <jarkko@kernel.org>
Subject: Re: [PATCH 0/3] sign-file,extract-cert: switch to PROVIDER API for OpenSSL >= 3.0
Date: Fri, 20 Sep 2024 18:34:21 +0300 [thread overview]
Message-ID: <D4B7ZCR4XWCT.3TWNN24TA8PSF@iki.fi> (raw)
In-Reply-To: <CAEg-Je_MXyP_PNj_QOu66SW_XYHy0zv0PnTTxX2qWELRG+xM_w@mail.gmail.com>
On Fri Sep 20, 2024 at 2:42 PM EEST, Neal Gompa wrote:
> On Tue, Aug 6, 2024 at 4:27 PM Neal Gompa <neal@gompa.dev> wrote:
> >
> > On Friday, July 12, 2024 3:11:13 AM EDT Jan Stancek wrote:
> > > The ENGINE interface has its limitations and it has been superseded
> > > by the PROVIDER API, it is deprecated in OpenSSL version 3.0.
> > > Some distros have started removing it from header files.
> > >
> > > Update sign-file and extract-cert to use PROVIDER API for OpenSSL Major >=
> > > 3.
> > >
> > > Tested on F39 with openssl-3.1.1, pkcs11-provider-0.5-2,
> > > openssl-pkcs11-0.4.12-4 and softhsm-2.6.1-5 by using same key/cert as PEM
> > > and PKCS11 and comparing that the result is identical.
> > >
> > > Jan Stancek (3):
> > > sign-file,extract-cert: move common SSL helper functions to a header
> > > sign-file,extract-cert: avoid using deprecated ERR_get_error_line()
> > > sign-file,extract-cert: use pkcs11 provider for OPENSSL MAJOR >= 3
> > >
> > > MAINTAINERS | 1 +
> > > certs/Makefile | 2 +-
> > > certs/extract-cert.c | 138 +++++++++++++++++++++++--------------------
> > > scripts/sign-file.c | 134 +++++++++++++++++++++--------------------
> > > scripts/ssl-common.h | 32 ++++++++++
> > > 5 files changed, 178 insertions(+), 129 deletions(-)
> > > create mode 100644 scripts/ssl-common.h
> >
> > The code looks fairly reasonable to me and behaves as expected.
> >
> > I have been actively using this patch set for several weeks now across
> > linux-6.9.y and now linux-6.10.y with good success.
> >
> > It is in use in production for Fedora Asahi Linux kernels with good success.
> > Thanks for the fixes. :)
> >
> > Reviewed-by: Neal Gompa <neal@gompa.dev>
> >
>
> Jarkko, could you please consider submitting this for inclusion into
> 6.12? I've been carrying this for three Linux kernel rebases now
> (6.9.y, 6.10.y, and now 6.11.y) and it seems to be just fine, and
> without it, I cannot build kernels anymore with the OpenSSL engine API
> disabled in Fedora and CentOS/RHEL. I also expect that the engine API
> will disappear on other platforms in the near future given its
> deprecated status and recently accelerated conversion of engine
> backends to the newer provider API.
>
> Thanks in advance! :)
Yes, I think I can. And I've yet to do 6.12 PR because I've been
busy sorting out perf regression in the TPM driver.
ERROR: need consistent spacing around '*' (ctx:WxV)
#66: FILE: certs/extract-cert.c:69:
+ OSSL_STORE_CTX *store;
^
ERROR: need consistent spacing around '*' (ctx:WxV)
#93: FILE: certs/extract-cert.c:96:
+ ENGINE *e;
^
ERROR: need consistent spacing around '*' (ctx:WxV)
#199: FILE: scripts/sign-file.c:114:
+ OSSL_STORE_CTX *store;
^
ERROR: need consistent spacing around '*' (ctx:WxV)
#229: FILE: scripts/sign-file.c:141:
+ ENGINE *e;
^
Any ideas of these? My guess is that they are unfixable and related
to non-kernel-standard code.
BR, Jarkko
next prev parent reply other threads:[~2024-09-20 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1720728319.git.jstancek@redhat.com>
2024-08-06 20:27 ` [PATCH 0/3] sign-file,extract-cert: switch to PROVIDER API for OpenSSL >= 3.0 Neal Gompa
2024-09-20 11:42 ` Neal Gompa
2024-09-20 15:34 ` Jarkko Sakkinen [this message]
2024-09-20 20:05 ` Jan Stancek
2024-09-20 22:16 ` 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=D4B7ZCR4XWCT.3TWNN24TA8PSF@iki.fi \
--to=jarkko.sakkinen@iki.fi \
--cc=asahi@lists.linux.dev \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=j@jannau.net \
--cc=jarkko@kernel.org \
--cc=jstancek@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=neal@gompa.dev \
--cc=zxu@redhat.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