Re:SUSE Liberty Linux: secure your Linux future without fea...
by throwawayExSUSE on Monday July 03, 2023 @11:38AM
(#36574472)
The product was called "expanded support" before. It was used to buy companies out of their RHEL contract before the renewal date, and ship SLES for new deployments. Nothing new.
Re:SUSE Liberty Linux: secure your Linux future without fea...
by chadcatlett on Monday July 03, 2023 @12:10PM
(#36574994)
Ahh yes, there was that kind of thing as well. SUSE provided us with ways of replacing all packages on a RHEL running system with SUSE augmented CentOS packages. It was often used by people who wanted a cheaper alternative to RHEL, but still wanted CentOS for their random 3rd party apps.
Re:SUSE Liberty Linux: secure your Linux future without fea...
by tripflag on Monday July 03, 2023 @05:06PM
(#36578828)
Curious, what CVE is this? I thought that even CentOS 7.x was still under support, so not patching vulnerabilities sounds like a great way to lose even more (would-be) customers.
Re:SUSE Liberty Linux: secure your Linux future without fea...
by galangalalgol on Monday July 03, 2023 @10:54PM
(#36581644)
It looks like they finished fixing it last week and it looks like it was only a high. When I first ran into it in audit reports python said it wasn't a defect in python, just how it was used, but they would change it in 3.11.4 but no official backports. The bugzilla issue for 7 and 8 said they couldn't fix it without breaking things, so they wouldn't. It seems they found a way. https://access.redhat.com/security/cve/cve-2023-24329
Re:SUSE Liberty Linux: secure your Linux future without fea...
by worthless-trash on Monday July 03, 2023 @10:01PM
(#36581270)
Citation ? as Criticals are -definitely- still in el7 lifecycle support.
Re:SUSE Liberty Linux: secure your Linux future without fea...
by galangalalgol on Monday July 03, 2023 @10:55PM
(#36581647)
Repeating from sibling post to make sure I'm not leaving any misinformation spread.
It looks like they finished fixing it last week and it looks like it was only a high. When I first ran into it in audit reports python said it wasn't a defect in python, just how it was used, but they would change it in 3.11.4 but no official backports. The bugzilla issue for 7 and 8 said they couldn't fix it without breaking things, so they wouldn't. It seems they found a way. https://access.redhat.com/security/cve/cve-2023-24329
The auditors being happy is important, but part of what people pay for with RHEL is liability, and I can't imagine you get that with third party support.