Date: Wed, 17 Feb 2016 15:43:17 +0200 From: Tommi Pernila <tommi.pernila@iki.fi> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: CVE-2015-7547: critical bug in libc Message-ID: <CABHD1wSww%2B8ooksvk7oz4nY7W96gUmW68XDGHimugXPEDT0m%2Bw@mail.gmail.com> In-Reply-To: <20160217142410.18748906@freyja.zeit4.iv.bundesimmobilien.de> References: <20160217142410.18748906@freyja.zeit4.iv.bundesimmobilien.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, as Shawn types faster then me... the libc issue has been found from glibc which is not used in the BSD family. This is the affected libc https://en.wikipedia.org/wiki/GNU_C_Library What FreeBSD uses: https://en.wikipedia.org/wiki/BSD_libc -Tommi On Wed, Feb 17, 2016 at 3:24 PM, O. Hartmann <ohartman@zedat.fu-berlin.de> wrote: > It is around now in the media also for non-OS developers: CVE-2015-7547 > describes a bug in libc which is supposed to affects all Linux versions. > > big price question: is FreeBSD > 9.3 also affected? > > Some reporters tell us that Linux/UNIX is affected, so sometimes this > terminus > is used to prevent the "Linux-nailed" view, but sometimes it also referes > to > everything else those people can not imagine but consider them Linux-like. > So > I'm a bit puzzled, since there is no report about *BSD is affected, too. > > Thanks in advance for shedding light onto CVE-2015-7547. > > Regards, > > oh > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABHD1wSww%2B8ooksvk7oz4nY7W96gUmW68XDGHimugXPEDT0m%2Bw>