resolv and dynamic linking to compat libc

From: Lachlan O'Dea (odela01@ca.com)
Date: 06/27/02


Date: Thu, 27 Jun 2002 15:43:14 +1000
From: Lachlan O'Dea <odela01@ca.com>
To: freebsd-security@freebsd.org

Hi,

With regard the resolv vulnerability, is there any issue with older
binaries that are linking against an older libc.so? For example, on my
box I have a /usr/lib/compat/libc.so.3. Will a make world fix this
library as well?

Thanks.

-- 
Lachlan O'Dea <lodea@vet.com.au>          Computer Associates Pty Ltd
Webmaster                                   Vet - Anti-Virus Software
http://www.vet.com.au/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message


Relevant Pages

  • Re: resolv and dynamic linking to compat libc
    ... > With regard the resolv vulnerability, is there any issue with older ... > binaries that are linking against an older libc.so? ... thus leaving binaries that link against it vulnerable. ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)
  • Re: resolv and dynamic linking to compat libc
    ... > With regard the resolv vulnerability, is there any issue with older ... > binaries that are linking against an older libc.so? ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)
  • Re: char* pname = "Harry"
    ... for which there is no excuse. ... methods for linking C code written without regard to C++ arcane ...
    (comp.lang.c)
  • Re: GPL only modules
    ... and "linking" simply doesn't matter. ... to me distributing statically-linked binaries containing his library, ... other differences when it comes to distribution of the resulting ...
    (Linux-Kernel)
  • Re: char* pname = "Harry"
    ... for which there is no excuse. ... methods for linking C code written without regard to C++ arcane ...
    (comp.lang.c)