Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19417 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58649 invoked by uid 1010); 5 Oct 2005 06:37:34 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 58634 invoked from network); 5 Oct 2005 06:37:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Oct 2005 06:37:34 -0000 X-Host-Fingerprint: 69.225.174.131 69-225-174-131.ded.pacbell.net Windows 2000 SP2+, XP SP1 (seldom 98 4.10.2222) Received: from ([69.225.174.131:36859] helo=x.win.covalent.net) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 1B/8E-54476-DA473434 for ; Wed, 05 Oct 2005 02:37:34 -0400 Received: from [192.168.0.21] ([24.13.128.132]) by x.win.covalent.net over TLS secured channel with Microsoft SMTPSVC(5.0.2195.6713); Tue, 4 Oct 2005 23:35:57 -0700 Message-ID: <4343746C.4080908@rowe-clan.net> Date: Wed, 05 Oct 2005 01:36:28 -0500 User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ron Korving CC: internals@lists.php.net References: <433973F4.2020103@ibink.com> <43397815.2030000@lerdorf.com> <4342A4A8.9090103@ibink.com> <362F3EA1-D850-429E-8889-54675FCEB920@omniti.com> <4342ACC1.2030106@ibink.com> <74.A2.54476.28AC2434@pb1.pair.com> <4342E9BB.1010902@ibink.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 05 Oct 2005 06:35:58.0250 (UTC) FILETIME=[0B9480A0:01C5C977] Subject: Re: [PHP-DEV] Comment on Bug #30153: FATAL erealloc() error whenusinggzinflate() From: wrowe@rowe-clan.net ("William A. Rowe, Jr.") Perhaps this is a stupid question, but has anyone ensured that zlib rev 1.2.3 still exhibits this behavior? The trouble ticket is close to useless for recapping this; but I'm happy to shepard a fix or some solution through the zlib dev team. The ticket indiciated that PHP is using it's own fork of zlib, perhaps I'm confused on the issue, though. All versions pre-1.1.4 and pre-1.2.3 are known-vulnerable, so there's really no point in reproducing these problems on anything other than the current rev 1.2.3. Bill Ron Korving wrote: > My bad, I remembered the initial post wrong. Still, the primary bug report > should be for the zlib fellas. They're the ones who need to fix their lib. > Secondary, maybe php folks can see if the problem can be worked around. But > still, the guys with the real problem are the zlib guys. Have you filed a > bugreport there? That should be the primary action in this situation.