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.
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
