linux-fscrypt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: "Aleksander Adamowski" <olo@fb.com>,
	"Tomasz Kłoczko" <kloczko.tomasz@gmail.com>
Cc: "linux-fscrypt@vger.kernel.org" <linux-fscrypt@vger.kernel.org>
Subject: Re: [fsverity-utils] 1.4: test suite does not build
Date: Wed, 22 Sep 2021 11:57:36 -0700	[thread overview]
Message-ID: <YUt8oAgoapdvJREi@sol.localdomain> (raw)
In-Reply-To: <SA1PR15MB4824F4BC9969A55AFD556182DDA09@SA1PR15MB4824.namprd15.prod.outlook.com>

On Mon, Sep 20, 2021 at 09:52:55PM +0000, Aleksander Adamowski wrote:
> On Mon, Sep 20, 2021 at 2:19 PM, Eric Biggers wrote:
> 
> > Aleksander: there still shouldn't be any compiler warnings.  In my test script
> > (scripts/run-tests.sh) I actually use -Werror.  If there isn't a good way to
> > avoid these deprecation warnings (and I'd prefer not to have code that's
> > conditional on different OpenSSL versions), we can just add
> > -Wno-deprecated-declarations to the Makefile for now.
> 
> I think -Wno-deprecated-declarations is the best option for now.
> 
> I took a few looks around and the community isn't ready for OpenSSL 3.0 just
> yet with PKCS#11 support.
> 
> The release happened just 2 weeks ago.
> 
> Projects like libp11 (https://github.com/OpenSC/libp11), the PKCS#11 engine
> implementation for OpenSSL, haven't yet caught up to that fact - there's no
> trace of discussion about migrating to the Providers API anywhere on their
> mailing lists or issue tracker.
> 
> The official OpenSSL release does not come with a PKCS#11 provider, and it only
> acknowledges a potential future existence of such in a single sentence in their
> design doc (https://www.openssl.org/docs/OpenSSL300Design.html):
> 
> "For example a PKCS#11 provider may opt out of caching because its algorithms
> may become available and unavailable over time."
> 
> Since this is a completely new, redesigned API, I expect it to take some time
> before alternatives to existing Engine-based implementations arise.

I've pushed out a change which adds -Wno-deprecated-declarations.

Tomasz, I'd still appreciate any details on what actually caused the test
programs to not build for you, as I can't reproduce it myself.

- Eric

      reply	other threads:[~2021-09-22 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 13:20 1.4: test suite does not build Tomasz Kłoczko
2021-09-18 20:04 ` [fsverity-utils] " Eric Biggers
2021-09-20 20:05   ` Aleksander Adamowski
2021-09-20 21:19     ` Eric Biggers
2021-09-20 21:52       ` Aleksander Adamowski
2021-09-22 18:57         ` 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=YUt8oAgoapdvJREi@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=kloczko.tomasz@gmail.com \
    --cc=linux-fscrypt@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).