home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!data.nas.nasa.gov!mustang.mst6.lanl.gov!nntp-server.caltech.edu!madler
- From: madler@cco.caltech.edu (Mark Adler)
- Newsgroups: comp.compression
- Subject: Re: Unzip50 bug??
- Date: 16 Nov 1992 22:12:48 GMT
- Organization: California Institute of Technology, Pasadena
- Lines: 18
- Message-ID: <1e96d0INNd9b@gap.caltech.edu>
- References: <1dunluINNekd@usenet.INS.CWRU.Edu>
- NNTP-Posting-Host: sandman.caltech.edu
-
-
- Yes, I would call that an Unzip 5.0 bug. Currently unzip does not
- stop when it exceeds the uncompressed byte count--it assumes that
- the input data is good, and that it will get an end-of-block marker
- in the compressed data. This is only true for the deflate method,
- since the other methods don't have end-markers, they depend on the
- counts (compressed or uncompressed) to stop.
-
- This was partly a speed trade-off, and partly laziness. I will look
- into putting checks for compressed and uncompressed sizes.
-
- This will always be a problem for funzip, since a filter generated
- zip file doesn't have the sizes at the start, since they are not
- known at the start. funzip will continue to depend on the markers
- in the compressed stream.
-
- Mark Adler
- madler@cco.caltech.edu
-