AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2016.10.28 18:50 "[Tiff] New release ? + remaining CVE tickets", by Even Rouault
2016.10.28 19:24 "Re: [Tiff] New release ? + remaining CVE tickets", by Bob Friesenhahn
2016.12.13 04:56 "[Tiff] one little ill-advised change in v4.0.7 broke functionality for HylaFAX", by Lee Howard
2016.12.13 08:54 "Re: [Tiff] one little ill-advised change in v4.0.7 broke functionality for HylaFAX", by Even Rouault
2016.12.13 17:40 "Re: [Tiff] one little ill-advised change in v4.0.7 broke functionality for HylaFAX", by Lee Howard
2016.12.13 18:06 "Re: [Tiff] one little ill-advised change in v4.0.7 broke functionality for HylaFAX", by Even Rouault
2016.12.13 18:52 "Re: [Tiff] one little ill-advised change in v4.0.7 broke functionality for HylaFAX", by Lee Howard
2016.12.13 23:19 "Re: [Tiff] one_little_ill-advised_change_in_v4.0.7_brok e_functionality_for_HylaFAX", by

2016.12.13 23:19 "Re: [Tiff] one_little_ill-advised_change_in_v4.0.7_brok e_functionality_for_HylaFAX", by

Od: Lee Howard <faxguy@howardsilvan.com>

Datum: 13. 12. 2016 19:55:04

"

It has its own copy of tif_fax3.h (which includes TIFFFaxTabEnt)...

https://sourceforge.net/p/hylafax/HylaFAX+/HEAD/tree/trunk/faxd/tif_fax3.h

(https://sourceforge.net/p/hylafax/HylaFAX+/HEAD/tree/trunk/faxd/tif_fax3.h)

Again, I have no doubt whatsoever that this could all be done cleaner/ better.  I'm just saying that it is what it is.

"

OK, I'll revert that with a prominent warning so that the next one that

touches this code is aware of those tricky aspects that cannot be

anticipated from libtiff code itself.

"

Thanks. you want to provide a code change for HylaFAX then I'm happy to consider it.   If

"

In my opinion that'd be better, as at this point affected users will need to upgrade *something*. Given that hylafax includes a "fork" of tif_fax3.h, it should also include a fork of tif_fax3sm.c, not import the tables (which are arguably leaked implementation detail) from libtiff.