Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>,
	<linux-mtd@lists.infradead.org>
Cc: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
Subject: Re: [PATCH] ubifs-utils: Don't compile engine support if not available
Date: Mon, 31 Aug 2026 09:50:18 +0800	[thread overview]
Message-ID: <481dc2f7-ba6f-743a-b841-a3bdb8807ff6@huawei.com> (raw)
In-Reply-To: <20260829173245.5-tFbtxE@breakpoint.cc>

在 2026/8/30 1:32, Sebastian Andrzej Siewior 写道:
> OpenSSL 4.0 dropped engine support which was deprecated since 3.0. The
> replacement is the "providers" API.
> 
> Add an ifndef OPENSSL_NO_ENGINE around the engine code so it can be left
> out where it is not supported.
> 
> Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
> ---
>   ubifs-utils/common/sign.c | 10 +++++++++-
>   1 file changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git a/ubifs-utils/common/sign.c b/ubifs-utils/common/sign.c
> index 032a6acc045d..5f94c0ad176f 100644
> --- a/ubifs-utils/common/sign.c
> +++ b/ubifs-utils/common/sign.c
> @@ -23,11 +23,14 @@
>   #include <openssl/bio.h>
>   #include <openssl/pem.h>
>   #include <openssl/err.h>
> -#include <openssl/engine.h>
>   #include <openssl/cms.h>
>   #include <openssl/conf.h>
>   #include <err.h>
>   
> +#ifndef OPENSSL_NO_ENGINE
> +#include <openssl/engine.h>
> +#endif
> +
>   #include "linux_types.h"
>   #include "sign.h"
>   #include "ubifs.h"
> @@ -139,6 +142,7 @@ static EVP_PKEY *read_private_key(const char *private_key_name, X509 **cert)
>   	*cert = NULL;
>   
>   	if (!strncmp(private_key_name, "pkcs11:", 7)) {
> +#ifndef OPENSSL_NO_ENGINE
>   		ENGINE *e;
>   		struct {
>   			const char *url;
> @@ -177,6 +181,10 @@ static EVP_PKEY *read_private_key(const char *private_key_name, X509 **cert)
>   		}
>   		*cert = parms.cert;
>   		fprintf(stderr, "Using cert %p\n", *cert);
> +#else
> +		ssl_err_msg("PKCS#11 ENGINE support not available.");
> +		return NULL;
Hi Sebastian,
Thanks for pointing that. I am wondering whether it would be better to 
implement PKCS11 encryption in #else branch by the OpenSSL 4.0 API provider.
> +#endif
>   	} else {
>   		BIO *b;
>   
> 


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2026-08-31  1:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-29 17:32 [PATCH] ubifs-utils: Don't compile engine support if not available Sebastian Andrzej Siewior
2026-08-31  1:50 ` Zhihao Cheng [this message]
2026-08-31  6:25   ` Sebastian Andrzej Siewior

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=481dc2f7-ba6f-743a-b841-a3bdb8807ff6@huawei.com \
    --to=chengzhihao1@huawei.com \
    --cc=david.oberhollenzer@sigma-star.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sebastian@breakpoint.cc \
    /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