Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	jglong3 AT att DOT net
To:	cygwin AT cygwin DOT com
Subject:	ZLIB
Date:	Tue, 07 Sep 2004 18:29:05 +0000
Message-Id:	<090720041829.5116.413DFDF100033E40000013FC2160280748CC090201040906@att.net>
X-Authenticated-Sender:	amdsb25nM0BhdHQubmV0
X-IsSubscribed:	yes

Hello,

And, Thanks for your time, advise, and help!   :) :)

I am a newbie at CYGWIN and the CYGWIN SHELL environment. I apologize if this is the wrong forum for this subject and if this is a subject that does not relate to zlib in CYGWIN.

The following subject was researched in the CYGWIN Archives. If the answer exists, I apologize if the proper string(s) were not input to find the answer to the following discussion.

    A report by SecurityTracker mentions that there is situation in zlib.
    This situation in zlib is reported as relative to the inflate() and 
    inflateBack().
    The report says the situation varies depending on the application 
    using the zlib library, but if exploited can result in a denial of services.

Is there a new zlib to correct for this????

If so is the correction in Zlib or the cygwin.dll------

What download file or files are required????

THANKS for your time, help, and advise!!! :)

Jerry

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -