From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Forthcoming OpenSSL Releases Date: Fri, 26 May 2023 15:28:32 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9216611924968885115==" List-Id: --===============9216611924968885115== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Thank you very much for letting me know. I wasn=E2=80=99t aware at all. I reverted those changes in next and if the build goes through I will merge t= he branch back into master again. -Michael > On 26 May 2023, at 14:33, Adolf Belka wrote: >=20 > Hi, >=20 > On 24/05/2023 11:02, Michael Tremer wrote: >> Hello, >>> On 24 May 2023, at 09:47, Adolf Belka wrote: >>>=20 >>> Hi Michael, >>>=20 >>> On 24/05/2023 10:07, Michael Tremer wrote: >>>> It looks like we might not want to release the forthcoming Core Update b= efore this. >>>>=20 >>>> I did not hear any rumours about what might be the issue, but I would sa= y that it wouldn=E2=80=99t hurt us to wait. >>>>=20 >>>> What other outstanding issues do we have that are currently blocking the= update? >>>>=20 >>> The fix for Bug#13117 has been merged into master so that is no longer bl= ocking. >>>=20 >>> 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 teste= rs reporting in the forum. I am making progress on this but there are still s= ome bits outstanding. The bug has been around for a long time so it won't hur= t for it to wait till Core Update 176. >> Okay. Let=E2=80=99s rather have the right fix than a quick one. I agree! > The reversion of the update.sh script was done two days ago but there are 4= other commits for the same bug fix that also need to be reverted. >=20 > https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3D762c88ec4d85e3a4f= 7265b887f054cbe7703eb7c > https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3D82822934ba769bca4= 235cd2a02f848cdc8511120 > https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3D070abb0d011ff71e5= aefd170dcb366d81bdf2497 > https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3D18bece0edbd817933= f48fdbffcffffd074e42c05 >=20 > just to make sure that those don't get missed. >=20 > Regards, > Adolf. >>> I haven't found anything else that was a problem and I haven't seen any o= ther issues mentioned in the forum that look to be caused by CU175. >> That sounds good then! >>> Regards, >>> Adolf. >>>> -Michael >>>>=20 >>>>> Begin forwarded message: >>>>>=20 >>>>> From: Tomas Mraz >>>>> Subject: Forthcoming OpenSSL Releases >>>>> Date: 24 May 2023 at 05:06:12 BST >>>>> To: "openssl-project(a)openssl.org" , "o= penssl-users(a)openssl.org" , openssl-announce(a= )openssl.org >>>>> Reply-To: openssl-users(a)openssl.org >>>>>=20 >>>>> 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. >>>>>=20 >>>>> These releases will be made available on Tuesday 30th May 2023 >>>>> between 1300-1700 UTC. >>>>>=20 >>>>> These are security-fix releases. The highest severity issue fixed in >>>>> each of these three releases is Moderate: >>>>>=20 >>>>> https://www.openssl.org/policies/secpolicy.html >>>>>=20 >>>>> Yours >>>>> The OpenSSL Project Team >>>>>=20 >>>>=20 >>>=20 >>> --=20 >>> Sent from my laptop --===============9216611924968885115==--