Re: [Security-Discuss] updated glibc to be compatible with _what_ new kernels
Vincent Danen <vdanen-4qZELD6FgxhWk0Htik3J/[email protected]> Wed, 11 Oct 2006 14:56:30 -0600
| Newsgroups | gmane.linux.mandrake.security.general |
|---|---|
| Message-ID | <[email protected]> |
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-25--243119278 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Oct-11-06, at 11:59 AM, Robert M. Riches Jr. wrote: >> From: Stew Benedict <sbenedict-4qZELD6FgxhWk0Htik3J/[email protected]> >> Subject: Re: [Security-Discuss] updated glibc to be compatible >> with _what_ >> new kernels >> >> On Wed, 11 Oct 2006, Robert M. Riches Jr. wrote: >> >>> Advisory MDKA-2006:037, including >>> 2006.0/i586/glibc-2.3.6-4.1.20060mdk.i586.rpm, says the >>> following: >>> >>> Updated glibc packages are being provided to ensure >>> that kernel and user-space tools are in sync. This >>> update also fixes a bug present on x86_64 platforms >>> where strncmp() is mis-optimized. >>> >>> _What_ new kernels need the new glibc? Is it the kernel update >>> from a few weeks ago, 2.6.12-25mdk? Or, is it a new kernel not >>> yet visible in the updates list? >>> >> >> A kernel update that is going out now. We were waiting for >> communication >> from QA before releasing it. Sorry about the confusion. > > Thanks for the info. > > It will be helpful if the info about the kernel update has > more detail on the (in)compatibility issues between the old > and new glibc and kernel. Specifically, the normal strategy > for a kernel update is to leave the old kernel installed as > a fallback in case of problems with the new one (as in the > DoS bug in -23 and -24). If it turns out that the new > kernel won't work with the old glibc, and the old kernel > won't work with the new glibc, that would eliminate the > option of switching between old and new kernels. You don't have to worry about that. The new glibc will work with both old and new kernels, and the old glibc will also work with both. There are no constraints as to any specific version requirements for either. -- {FEE30AD4 : 7F6C A60C 06C2 4811 FA1C A2BC 2EBC 5E32 FEE3 0AD4} mysql> SELECT * FROM users WHERE clue > 0; Empty set (0.00sec) --Apple-Mail-25--243119278 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFLVqDLrxeMv7jCtQRAtNVAJ9IndE7F50SRFLUTK59uORBfatalQCdFT8P J8eY59PtF8WStO2fLV5V7ns= =TZSt -----END PGP SIGNATURE----- --Apple-Mail-25--243119278--