Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#73528 - glibc: CVEs noted in glibc-2.33
Attached to Project:
Arch Linux
Opened by Andrew (abrouwers) - Thursday, 27 January 2022, 14:34 GMT
Last edited by freswa (frederik) - Friday, 11 February 2022, 16:13 GMT
Opened by Andrew (abrouwers) - Thursday, 27 January 2022, 14:34 GMT
Last edited by freswa (frederik) - Friday, 11 February 2022, 16:13 GMT
|
DetailsDescription:
Recently, I noticed that another distro I use patched glibc-2.33 for some recent CVEs reported/fixed upstream. Unfortunately, it seems like the arch glibc package (well, toolchain) is not actively maintained at the moment. Any chance to at least address the open CVEs? https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/release/2.33/master |
This task depends upon
Closed by freswa (frederik)
Friday, 11 February 2022, 16:13 GMT
Reason for closing: Fixed
Additional comments about closing: glibc-2.35 in [testing]
Friday, 11 February 2022, 16:13 GMT
Reason for closing: Fixed
Additional comments about closing: glibc-2.35 in [testing]
Comment by T.J. Townsend (blakkheim) -
Sunday, 30 January 2022, 15:15 GMT
Could the security fixes be backported to the current version until someone decides enough is enough with the old toolchain?