Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Mar 2002 02:26:51 +0100
From:      Sune Stjerneby <sst@vmunix.dk>
To:        "Thomas T. Veldhouse" <veldy@veldy.net>
Cc:        freebsd-security@FreeBSD.ORG
Subject:   Re: zlib overflow problem?
Message-ID:  <20020312022651.A14838@fnyx.vmunix.dk>
In-Reply-To: <00e101c1c942$b6bfeb60$3028680a@tgt.com>; from veldy@veldy.net on Mon, Mar 11, 2002 at 03:21:30PM -0600
References:  <00d601c1c941$56be3dd0$3028680a@tgt.com> <20020311131442.D77202@rain.macguire.net> <00e101c1c942$b6bfeb60$3028680a@tgt.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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.
> 
> Here is the RedHat posting.  They don't even mention any changes or updates
> to glibc.

The zlib bug is an issue on Linux-systems due to the brokeness of
glibc malloc.

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.

-- 
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?20020312022651.A14838>