This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: glibc 2.5 - patch for GHOST (CVE-2015-0235)


On 04/21/2015 04:47 PM, czezz wrote:
> Well, that was my initial idea.
> But as only I looked little bit deeper I realized I cannot go like that.
> Some of patches from your repository/link contain lines like following:
> glibc-rh947882.patch:diff -urN glibc-2.5-20061008T1257.orig/sysdeps/posix/getaddrinfo.c glibc-2.5-20061008T1257/sysdeps/posix/getaddrinfo.c
> glibc-rh947882.patch:--- glibc-2.5-20061008T1257.orig/sysdeps/posix/getaddrinfo.c       2013-04-11 14:41:39.224166628 -0400
> glibc-rh947882.patch:+++ glibc-2.5-20061008T1257/sysdeps/posix/getaddrinfo.c    2013-04-11 15:30:32.186995962 -0400
> so, the script for building in your repository expects to have source files/some of source files in dir glibc-2.5-20061008T1257/
> where in Slackware's building script it is glibc-2.5/
> Of course I can re-tar and re-compress Slackware's source glibc but then I must modify all Slack's diff files (which is in the end and idea).
> Im more worried that I have compared eg:
> glibc-rh645672.patch with glibc.CVE-2010-3856.diff.gz. They are similar but not identical...

Ah, I misunderstood you.  I assumed that you were attempting to backport
a single fix.  If you want to reach bug fix parity with a still-support
glibc (be it from Debian, Red Hat or SuSE), that is going to be a *lot*
more work.

-- 
Florian Weimer / Red Hat Product Security


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]