From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: "Wang, Kuiying" <kuiying.wang@intel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"Jia, Chunhui" <chunhui.jia@intel.com>,
"Shi, Yilei" <yilei.shi@intel.com>,
"Mihm, James" <james.mihm@intel.com>,
"Xu, Qiang" <qiang.xu@intel.com>
Subject: Re: OpenBMC CVE issues in openssl
Date: Tue, 24 Sep 2019 07:11:52 -0400 [thread overview]
Message-ID: <A939C572-3918-43F2-A444-5211C49EF17A@fuzziesquirrel.com> (raw)
In-Reply-To: <959CAFA1E282D14FB901BE9A7BF4E7724E52C90B@shsmsx102.ccr.corp.intel.com>
at 10:48 PM, Wang, Kuiying <kuiying.wang@intel.com> wrote:
> Hi Brad,
> Ok sure.
> I prefer to upgrading openssl related separately first and then others.
> Because I have urgent requirement for the latest version to fix security
> issues, do you agree on that?
>
> That means I submit another patch just to upgrading openssl to 1.1.1d, is
> it acceptable?
Hi Kwin
I merged 25306 this morning which contains 1.1.1d.
thx - brad
next prev parent reply other threads:[~2019-09-24 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 2:25 OpenBMC CVE issues in openssl Wang, Kuiying
2019-09-24 2:41 ` Brad Bishop
2019-09-24 2:48 ` Wang, Kuiying
2019-09-24 11:11 ` Brad Bishop [this message]
2019-09-25 1:22 ` Wang, Kuiying
2020-05-07 7:43 ` openssl upgrade chunhui.jia
2020-05-07 16:54 ` openssl upgrade CVE-2020-1967 Joseph Reynolds
2020-05-08 0:27 ` chunhui.jia
-- strict thread matches above, loose matches on Subject: below --
2019-09-18 6:05 OpenBMC CVE issues in openssl Xu, Qiang
2019-09-18 14:49 ` Brad Bishop
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=A939C572-3918-43F2-A444-5211C49EF17A@fuzziesquirrel.com \
--to=bradleyb@fuzziesquirrel.com \
--cc=chunhui.jia@intel.com \
--cc=james.mihm@intel.com \
--cc=kuiying.wang@intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=qiang.xu@intel.com \
--cc=yilei.shi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.