2008.08.29 22:53 "[Tiff] Some security fixes from RHEL", by Even Rouault

2008.09.01 18:45 "Re: [Tiff] Some security fixes from RHEL", by Bob Friesenhahn

Maybe it's better if I just post it online:

        http://prive.bitwizard.nl/htdocs/tifftest.tgz

My guess is that running it will give you some corner cases within the hour. Debugging those should take about an hour each. And fixing it

The package looks useful.

For my own testing, I have found it useful to use Unix 'ulimit' to limit how many seconds the code is allowed to run. For example 'ulimit -t 3'. A pretty common problem is code which runs far too long, or even forever.

It is best to run the code with a malloc debug library as well as with stack checking/barriers in place to detect any attempt to overwrite the stack. I am not sure if GCC supports the stack checking feature so some other compiler may be required.

Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/