AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2007.11.02 20:26 "[Tiff] Recent bug fixes in CVS head", by Frank Warmerdam
2007.11.21 18:52 "[Tiff] tag content size limit?", by Frank Warmerdam
2007.11.22 08:05 "RE: [Tiff] tag content size limit?", by Tillaart, Rob van den
2008.01.14 12:02 "回复: RE: [Tiff] TIFFWriteScanline - wr ite band orders", by gis geo
2008.01.14 06:32 "[Tiff] TIFFWriteScanline - write band orders", by gis geo
2008.01.14 07:25 "RE: [Tiff] TIFFWriteScanline - write band orders", by Tillaart, Rob van den
2007.12.30 22:20 "[Tiff] libtiff4 - tests failing - TIFF_SETGET_UNDEFINED for some tags", by Frank Warmerdam
2007.12.30 23:07 "Re: [Tiff] libtiff4 - tests failing - TIFF_SETGET_UNDEFINED for some tags", by Frank Warmerdam
2007.12.30 23:59 "Re: [Tiff] libtiff4 - tests failing - TIFF_SETGET_UNDEFINED for some tags", by Bob Friesenhahn

2007.11.21 18:52 "[Tiff] tag content size limit?", by Frank Warmerdam

Joris,

I have run into problems with my attempts to create a TIFF file with 1333333 strips. Attempts to read the the stripoffsets tag results in an error in TIFFReadDirEntryErr() with this logic:

        if ((uint64)(4*1024*1024/typesize)<direntry->tdir_count)
                return(TIFFReadDirEntryErrSizesan);
        if ((uint64)(4*1024*1024/desttypesize)<direntry->tdir_count)
                return(TIFFReadDirEntryErrSizesan);

The logic seems to assume that any tag contents larger than 4MB likely implies a corrupt file. Is there a particular reason we should put in place such a restriction? Should the restriction be removed? Relaxed? (perhaps upped to any tag value larger than 1GB is likely corruption? or any tag value larger than the file itself is?

Best regards,
--
---------------------------------------+--------------------------------------

I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam

and watch the world go round - Rush    | President OSGeo, http://osgeo.org