From: Marcel Holtmann <marcel at holtmann.org>
To: ell at lists.01.org
Subject: Re: [PATCH] build: Check for openssl legacy provider requirement
Date: Fri, 20 May 2022 11:13:55 +0200 [thread overview]
Message-ID: <0373E38A-FD24-457D-B4DE-DFB4A9F91DCD@holtmann.org> (raw)
In-Reply-To: 20220519224828.91435-1-mathew.j.martineau@linux.intel.com
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Hi Mat,
> OpenSSL 3 introduced some command line incompatibilities and removed
> some old algorithms from the defaults. This broke some of the unit test
> cert generation commands on distros like Ubuntu 22.04 and Fedora 36.
>
> Detect support of "providers" by the system openssl command and insert
> the necessary command line parameters to enable legacy algorithms for
> openssl v3, but leave the commands unchanged for older openssl versions.
> ---
>
> Tested on Ubuntu 22.04, Fedora 36, and Fedora 35.
>
> ---
> Makefile.am | 26 ++++++++++++++++++--------
> configure.ac | 3 +++
> 2 files changed, 21 insertions(+), 8 deletions(-)
what would it take to just use OpenSSL 3 since these are just required on the development systems. I need to check my release system since that is historically always behind, but I feel this business of supporting two OpenSSL versions will get out of hand quickly. It is too bad that we can not generate the certificates with our own tools.
Regards
Marcel
next reply other threads:[~2022-05-20 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 9:13 Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-21 0:15 [PATCH] build: Check for openssl legacy provider requirement Mat Martineau
2022-05-19 22:48 Mat Martineau
2022-06-29 13:59 ` Marcel Holtmann
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=0373E38A-FD24-457D-B4DE-DFB4A9F91DCD@holtmann.org \
--to=ell@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).