Description of problem: Mageia 1 Alpha 2 use glibc 2.12.1 release but the latest stable version is 2.13.0. Please upgrade it from 2.12.1 (2010-08-03) to 2.13.0 (2011-02-01) to fix bugs and fix security problem. glibc 2.12.90-18 to 2.13.0 changelog available at http://www.mail-archive.com/package-announce@lists.fedoraproject.org/msg19754.html and glibc 2.12.2 changelog available at http://lists.fedoraproject.org/pipermail/package-announce/2010-December/052580.html Sources: http://ftp.gnu.org/gnu/glibc/glibc-2.13.tar.gz For better information, latest alsa release in several Linux Distribution : Fedora 15 rawhide use 2.13.90 et Fedora 14 use 2.12.90 OpenSuse 11.4 and factory use 2.11.3 Debian unstable sid use 2.11.2 Ubuntu snapshot natty use 2.13 Mandriva cooker use 2.12.1 Version-Release number of selected component (if applicable): glibc-2.12.1-11.mga1 Reproducible: Steps to Reproduce:
CC: (none) => arnaud.patard
CC: (none) => misc
CC: (none) => dmorganec
CC: (none) => tmb
What security problem are you talking about ?
(In reply to comment #1) > What security problem are you talking about ? - Require suid bit on audit objects in privileged programs (CVE-2010-3856) - Never expand $ORIGIN in privileged programs (#643306, CVE-2010-3847)
glibc is not upgraded from 2.12.1 to 2.13.0 in Mageia 1 Beta 1. Then now, is it for Mageia 2 release ?
It will be done in Cauldron after Mageia 1 is released... There are still recent bugs showing up in glibc-2.13, so its not a "simple and safe" upgrade. We want a very stable Mageia 1
Target Milestone: --- => Mageia 2
(In reply to comment #4) > > It will be done in Cauldron after Mageia 1 is released... OK, no problems. > There are still recent bugs showing up in glibc-2.13, so its not a "simple and > safe" upgrade. > > We want a very stable Mageia 1 Me too.
no maintainer yet :(
CC: (none) => marja11
glibc 2.14.1 is now in updates-testing (cauldron)
Status: NEW => RESOLVEDResolution: (none) => FIXED