| Summary: | upgrade glibc from 2.12.1 to 2.13.0 (latest stable) to fix bugs and fix security problem | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Y.LE_NY <yleny> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | arnaud.patard, dmorganec, marja11, misc, tmb |
| Version: | Cauldron | ||
| Target Milestone: | Mageia 2 | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Y.LE_NY
2011-03-23 22:29:00 CET
Y.LE_NY
2011-03-23 22:30:10 CET
CC:
(none) =>
arnaud.patard
Y.LE_NY
2011-03-23 22:30:38 CET
CC:
(none) =>
misc
Y.LE_NY
2011-03-23 22:31:30 CET
CC:
(none) =>
dmorganec
Y.LE_NY
2011-03-23 22:31:55 CET
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. glibc 2.14.1 is now in updates-testing (cauldron) Status:
NEW =>
RESOLVED |