From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Forthcoming OpenSSL Releases
Date: Wed, 24 May 2023 10:02:11 +0100 [thread overview]
Message-ID: <8DF27C56-97B2-40B5-BCD6-9EDCCA433A76@ipfire.org> (raw)
In-Reply-To: <2c3addb2-69e3-f0de-2ac9-58268c9650eb@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2183 bytes --]
Hello,
> On 24 May 2023, at 09:47, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Michael,
>
> On 24/05/2023 10:07, Michael Tremer wrote:
>> It looks like we might not want to release the forthcoming Core Update before this.
>>
>> I did not hear any rumours about what might be the issue, but I would say that it wouldn’t hurt us to wait.
>>
>> What other outstanding issues do we have that are currently blocking the update?
>>
> The fix for Bug#13117 has been merged into master so that is no longer blocking.
>
> As mentioned to Peter, I recommend reverting my fix for Bug#11048 as some issues were found by myself (missed in my own testing) plus from other testers reporting in the forum. I am making progress on this but there are still some bits outstanding. The bug has been around for a long time so it won't hurt for it to wait till Core Update 176.
Okay. Let’s rather have the right fix than a quick one. I agree!
> I haven't found anything else that was a problem and I haven't seen any other issues mentioned in the forum that look to be caused by CU175.
That sounds good then!
> Regards,
> Adolf.
>> -Michael
>>
>>> Begin forwarded message:
>>>
>>> From: Tomas Mraz <tomas(a)openssl.org>
>>> Subject: Forthcoming OpenSSL Releases
>>> Date: 24 May 2023 at 05:06:12 BST
>>> To: "openssl-project(a)openssl.org" <openssl-project(a)openssl.org>, "openssl-users(a)openssl.org" <openssl-users(a)openssl.org>, openssl-announce(a)openssl.org
>>> Reply-To: openssl-users(a)openssl.org
>>>
>>> The OpenSSL project team would like to announce the forthcoming release
>>> of OpenSSL versions 3.0.9, 1.1.1u and 1.0.2zh. Note that OpenSSL 1.0.2
>>> is End Of Life and so 1.0.2zh will be available to premium support
>>> customers only.
>>>
>>> These releases will be made available on Tuesday 30th May 2023
>>> between 1300-1700 UTC.
>>>
>>> These are security-fix releases. The highest severity issue fixed in
>>> each of these three releases is Moderate:
>>>
>>> https://www.openssl.org/policies/secpolicy.html
>>>
>>> Yours
>>> The OpenSSL Project Team
>>>
>>
>
> --
> Sent from my laptop
next parent reply other threads:[~2023-05-24 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2c3addb2-69e3-f0de-2ac9-58268c9650eb@ipfire.org>
2023-05-24 9:02 ` Michael Tremer [this message]
2023-05-26 13:33 ` Adolf Belka
2023-05-26 14:28 ` Michael Tremer
2023-05-29 6:55 ` Peter Müller
2023-05-30 6:14 ` core175: merge kernel and alsa Arne Fitzenreiter
2023-05-30 8:45 ` Michael Tremer
2023-05-29 21:34 ` Forthcoming OpenSSL Releases Adolf Belka
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=8DF27C56-97B2-40B5-BCD6-9EDCCA433A76@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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