From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Shachar Menashe <shachar@vdoo.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [yocto-security] [PATCH] openssl: drop support for deprecated algorithms
Date: Wed, 23 Dec 2020 09:22:05 +0000 [thread overview]
Message-ID: <ae25e706b2f0074470d34553e14294ca77e5be55.camel@linuxfoundation.org> (raw)
In-Reply-To: <17790.1608715114795205463@lists.openembedded.org>
On Wed, 2020-12-23 at 01:18 -0800, Shachar Menashe wrote:
> Yeah, the patch is actually targeted for dunfell branch, but I
> understood the policy is first merging to master...
> So I will rebase the patch on master and retest everything
I did rebase the patch and its currently queued in master-next to see
how it worked out.
Khem has posted a good follow up showing it caused some issues for
recipes in meta-openembedded so we have a list of the software removing
those algorithms caused problems with.
We'd need to sort this out in master before we can think about dunfell.
Cheers,
Richard
prev parent reply other threads:[~2020-12-23 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM0PR08MB361713C43176BFA1C7295477C5C20@AM0PR08MB3617.eurprd08.prod.outlook.com>
2020-12-19 17:36 ` [yocto-security] [PATCH] openssl: drop support for deprecated algorithms Richard Purdie
2020-12-19 17:45 ` [OE-core] " Khem Raj
2020-12-19 17:45 ` Alexander Kanavin
2020-12-19 17:51 ` Khem Raj
2020-12-19 17:53 ` Konrad Weihmann
2020-12-19 17:58 ` Richard Purdie
2020-12-19 18:04 ` Konrad Weihmann
2020-12-20 0:08 ` Richard Purdie
2020-12-21 23:08 ` Andre McCurdy
2020-12-21 22:31 ` Mark Hatle
2020-12-20 4:33 ` Khem Raj
2020-12-23 1:53 ` Khem Raj
2020-12-23 9:18 ` Shachar Menashe
2020-12-23 9:22 ` Richard Purdie [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=ae25e706b2f0074470d34553e14294ca77e5be55.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=shachar@vdoo.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