From: Kristen Carlson Accardi <kristen@linux.intel.com>
To: Dave Hansen <dave.hansen@intel.com>,
linux-kernel@vger.kernel.org, Jarkko Sakkinen <jarkko@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Shuah Khan <shuah@kernel.org>
Cc: linux-sgx@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/sgx: Ignore OpenSSL 3.0 deprecated functions warning
Date: Thu, 21 Jul 2022 13:08:25 -0700 [thread overview]
Message-ID: <aa561e423906b175c73afbd6248a0a5dff0b079c.camel@linux.intel.com> (raw)
In-Reply-To: <bf154be9-1cc0-a555-47f5-04e5df1d6c31@intel.com>
On Thu, 2022-07-21 at 13:02 -0700, Dave Hansen wrote:
> On 7/21/22 12:40, Kristen Carlson Accardi wrote:
> > OpenSSL 3.0 deprecates some of the functions used in the SGX
> > selftests, causing build errors on new distros. For now ignore
> > the warnings until support for the functions is no longer
> > available.
>
> Are there some better functions we should be moving to?
I looked into this actually as my first choice, but the problem I had
was that the recommended new functions weren't available on other
OpenSSL libraries, and we'd have to add compatibility macros and stuff,
so it seemed to me that the less complicated thing to do was wait till
OpenSSL 1 was just not widely deployed anymore. This strategy is also
being used in other scripts in the kernel.
next prev parent reply other threads:[~2022-07-21 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 19:40 [PATCH] selftests/sgx: Ignore OpenSSL 3.0 deprecated functions warning Kristen Carlson Accardi
2022-07-21 20:02 ` Dave Hansen
2022-07-21 20:08 ` Kristen Carlson Accardi [this message]
2022-07-21 20:14 ` Dave Hansen
2022-07-28 8:00 ` 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=aa561e423906b175c73afbd6248a0a5dff0b079c.camel@linux.intel.com \
--to=kristen@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=shuah@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