Date: Tue, 12 Mar 2002 10:40:53 +0800 From: "David Xu" <davidx@viasoft.com.cn> To: "Sune Stjerneby" <sst@vmunix.dk>, "Thomas T. Veldhouse" <veldy@veldy.net> Cc: <freebsd-security@FreeBSD.ORG> Subject: Re: zlib overflow problem? Message-ID: <007901c1c96f$5825a720$ef01a8c0@davidwnt> References: <00d601c1c941$56be3dd0$3028680a@tgt.com> <20020311131442.D77202@rain.macguire.net> <00e101c1c942$b6bfeb60$3028680a@tgt.com> <20020312022651.A14838@fnyx.vmunix.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
how about /sys/net/ppp* ? -- David Xu ----- Original Message -----=20 From: "Sune Stjerneby" <sst@vmunix.dk> To: "Thomas T. Veldhouse" <veldy@veldy.net> Cc: <freebsd-security@FreeBSD.ORG> Sent: Tuesday, March 12, 2002 9:26 AM Subject: Re: zlib overflow problem? > On Mon, Mar 11, 2002 at 03:21:30PM -0600, Thomas T. Veldhouse wrote: > > Where did you see that information. I can not verify your = statement. > >=20 > > Here is the RedHat posting. They don't even mention any changes or = updates > > to glibc. >=20 > The zlib bug is an issue on Linux-systems due to the brokeness of > glibc malloc. >=20 > There aren't any changes or updates to glibc because this specific > issue was resolved within zlib; fixing the double free(), which > causes a warning on most systems but trouble on glibc-systems. >=20 > --=20 > Sune Stjerneby <sst@vmunix.dk> > - Part of an RFC 1876-compliant network. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?007901c1c96f$5825a720$ef01a8c0>