From: "akuster" <akuster808@gmail.com>
To: "Jan Lübbe" <jlu@pengutronix.de>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [zeus 0/7] Merge request
Date: Tue, 28 Apr 2020 10:09:15 -0700 [thread overview]
Message-ID: <1339637a-51fc-d092-1c71-903feca9d6c9@gmail.com> (raw)
In-Reply-To: <1ef6f737d5b44b11b409ed459438666b611b7fa9.camel@pengutronix.de>
On 4/28/20 9:13 AM, Jan Lübbe wrote:
> On Mon, 2020-04-27 at 19:15 -0700, akuster wrote:
>> Adrian Bunk (1):
>> openssl: Upgrade 1.1.1d -> 1.1.1e
>>
>> Alexander Kanavin (1):
>> openssl: update to 1.1.1f
> As 1.1.1g has been released to fix CVE-2020-1967
> https://www.openssl.org/news/secadv/20200421.txt
> maybe we should just update instead of picking Zhang Xiao's "openssl:
> fix CVE-2020-1967" (which would conflict with this PR).
Thanks for the information.
Once Master and then Dunfell have this update then Zeus can take it.
- armin
>
> Regards,
> Jan
>
next prev parent reply other threads:[~2020-04-28 17:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 2:15 [zeus 0/7] Merge request akuster
2020-04-28 2:15 ` [zeus 1/7] cve-check: CPE version '-' as all version akuster
2020-04-28 2:15 ` [zeus 2/7] pseudo: Ensure we use our own libsqlite akuster
2020-04-28 2:15 ` [zeus 3/7] wic: align layer plugin path akuster
2020-04-28 2:15 ` [zeus 4/7] inetutils: Use alternatives to avoid manpage conflict akuster
2020-04-28 2:15 ` [zeus 5/7] openssl: recommend cryptodev-module for corresponding PACKAGECONFIG akuster
2020-04-28 2:15 ` [zeus 6/7] openssl: Upgrade 1.1.1d -> 1.1.1e akuster
2020-04-28 2:15 ` [zeus 7/7] openssl: update to 1.1.1f akuster
2020-04-28 16:13 ` [OE-core] [zeus 0/7] Merge request Jan Luebbe
2020-04-28 17:09 ` akuster [this message]
2020-05-04 13:42 ` Jan Luebbe
2020-05-04 14:18 ` Steve Sakoman
2020-04-28 18:07 ` Martin Jansa
2020-04-29 4:35 ` Anuj Mittal
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=1339637a-51fc-d092-1c71-903feca9d6c9@gmail.com \
--to=akuster808@gmail.com \
--cc=jlu@pengutronix.de \
--cc=openembedded-core@lists.openembedded.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