From: Christian Melki <christian.melki@t2data.com>
To: oss-lists@triops.cz
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] openssl: Version bump. 1.1.1t -> 1.1.1s.
Date: Wed, 8 Feb 2023 11:35:47 +0100 [thread overview]
Message-ID: <a12aff59-3ba9-fcf2-644e-c413f264f8bf@t2data.com> (raw)
In-Reply-To: <Y+NtiCUINXgjN3Se@lenoch>
Oops!
mol acked changing it locally.
Thanks for pointing out my difficulties with alphabetical ordering. :D
/C
On 2/8/23 10:38 AM, Ladislav Michl wrote:
> Hi Christian!
>
> On Wed, Feb 08, 2023 at 09:01:07AM +0100, Christian Melki wrote:
>> Plug 4 CVEs.
>> https://www.openssl.org/news/cl111.txt
>> X.400 address type confusion in X.509 GeneralName (CVE-2023-0286)
>> Use-after-free following BIO_new_NDEF (CVE-2023-0215)
>> Double free after calling PEM_read_bio_ex (CVE-2022-4450)
>> Timing Oracle in RSA Decryption (CVE-2022-4304)
>
> seems bump text is reverted, should be 1.1.1s -> 1.1.1t...
>
> l.
>
next prev parent reply other threads:[~2023-02-08 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 8:01 Christian Melki
2023-02-08 9:38 ` Ladislav Michl
2023-02-08 10:35 ` Christian Melki [this message]
2023-02-08 11:50 ` [ptxdist] [APPLIED] openssl: Version bump. 1.1.1s -> 1.1.1t Michael Olbrich
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=a12aff59-3ba9-fcf2-644e-c413f264f8bf@t2data.com \
--to=christian.melki@t2data.com \
--cc=oss-lists@triops.cz \
--cc=ptxdist@pengutronix.de \
/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