From: Eric Biggers <ebiggers@kernel.org>
To: Disha Goel <disgoel@linux.ibm.com>
Cc: fsverity@lists.linux.dev, Aleksander Adamowski <olo@fb.com>
Subject: Re: OpenSSL engine removal and fsverity-utils compilation issue
Date: Mon, 17 Feb 2025 11:43:39 -0800 [thread overview]
Message-ID: <20250217194339.GE1258@sol.localdomain> (raw)
In-Reply-To: <20250123182436.GB2117666@google.com>
On Thu, Jan 23, 2025 at 06:24:36PM +0000, Eric Biggers wrote:
> On Thu, Jan 23, 2025 at 04:02:46PM +0530, Disha Goel wrote:
> > Hi,
> >
> > Some distributions have started removing OpenSSL engine support, replacing
> > engine.h with an empty dummy header file. As a result, fsverity-utils fails
> > to compile with the following error.
> >
> > Is there any plan to address this issue and support these distributions?
> >
> > Please seehttps://fedoraproject.org/wiki/Changes/OpensslDeprecateEngine for more details.
> >
> > # make
> > CC lib/compute_digest.o
> > CC lib/enable.o
> > CC lib/hash_algs.o
> > CC lib/sign_digest.o
> > lib/sign_digest.c: In function ‘load_pkcs11_private_key’:
> > lib/sign_digest.c:350:9: error: implicit declaration of function ‘ENGINE_load_dynamic’ [-Wimplicit-function-declaration]
> > 350 | ENGINE_load_dynamic();
> > | ^~~~~~~~~~~~~~~~~~~
>
> This is my first time hearing about this, but yes this has to be fixed. Thanks
> for reporting it.
>
> It's just the PKCS#11 token feature that is causing problems. This feature was
> contributed by Aleksander Adamowski <olo@fb.com> (Cc'ed) several years ago. I
> don't have much context on how/whether it is still being used.
>
> I'm tempted to just make the PKCS#11 token support conditional on
> !defined(OPENSSL_NO_ENGINE) for now. If someone still cares about PKCS#11 token
> support they can look into finding a way to keep it working with latest OpenSSL.
>
Now fixed in the master branch of fsverity-utils.
- Eric
prev parent reply other threads:[~2025-02-17 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 10:32 OpenSSL engine removal and fsverity-utils compilation issue Disha Goel
2025-01-23 18:24 ` Eric Biggers
2025-02-17 19:43 ` Eric Biggers [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=20250217194339.GE1258@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=disgoel@linux.ibm.com \
--cc=fsverity@lists.linux.dev \
--cc=olo@fb.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