Date: Mon, 2 Feb 2015 14:11:42 -0500 From: Robert Simmons <rsimmons0@gmail.com> To: freebsd-security@freebsd.org Subject: Re: Enumerating glibc dependencies Message-ID: <CA%2BQLa9CQd3GLYdK0BSUoosYVqn7ygkMOG4Cqb0CrAKsjDKtN7g@mail.gmail.com> In-Reply-To: <20150202185806.EC8B4884@hub.freebsd.org> References: <mailman.87.1422619202.67459.freebsd-security@freebsd.org> <20150202150721.E8553209@hub.freebsd.org> <20150202152243.GA29176@in-addr.com> <20150202164319.GL11558@ivaldir.etoilebsd.net> <alpine.BSF.2.00.1502020849580.24056@eboyr.pbz> <20150202185806.EC8B4884@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 2, 2015 at 1:58 PM, Roger Marquis <marquis@roble.com> wrote: >> Is FreeBSD glib always linked to libc (vs glibc)? > > > Apparently it is, at least on the systems I've tested where there were no > glibc dependencies at all. Another item added to the list of BSD > (security) advantages. I believe there is a bit of confusion on the list. My assumption for why the OP wants to determine glibc dependencies is the vulnerability in gethostbyname. However, many people on the list seem to be looking for devel/glib dependencies. devel/glib in FreeBSD's ports is unrelated to glibc (take a peek at the pkg-info file for this port for more info). GLib is a component of GNOME: https://developer.gnome.org/glib/ The library that contains the glibc vulnerability is the GNU C Library: https://www.gnu.org/software/libc/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BQLa9CQd3GLYdK0BSUoosYVqn7ygkMOG4Cqb0CrAKsjDKtN7g>