Lately my clients have been experiencing a lot of 'insufficient data' errors from PDFs created from tl-stdexten-fax-forasterisk. After speaking with Digium, it was suggested to remove the tiff2pdf conversion to prevent the errors from occurring, as a temporary bandaid until I have the conversion issue resolved. However, I cannot find where to do this in TL.
Any thoughts/ideas on how to bypass tiff2pdf or to diagnose/correct/troubleshoot the file conversion?
Thank you in advance for any input!
-Kevin
Submitted by eeman on Tue, 10/12/2010
Permalink
Submitted by eeman on Wed, 10/27/2010
Permalink
after some experimenting I
after some experimenting I think changing the tiff2pdf command in fax2pdf.sh to:
tiff2pdf -n -p letter -o ${FAXFILE}.pdf ${FAXFILE}.tif
results in fewer errors. I'd still advise against adobe though, purely from a gaping exploit standpoint.
actually digium is wrong on this one. I ran into this over the summer. Its an issue with recent versions of Adobe Acrobat Reader (9 point something). You have a very new version and its doing this to pdf's created by ghostscript. However, you should not be using Adobe Acrobat reader at ALL. This comes directly from Adobe themselves. Acrobat reader is full of more holes than Micro$oft code. Change your reader to something like Foxit and you wont have an issue, but whatever you do, for your own safety, stop using Acrobat Reader.
http://news.cnet.com/8301-1009_3-10224449-83.html
http://www.zdnet.com/blog/security/adobe-warns-of-flash-pdf-zero-day-at…
http://www.zdnet.com/blog/security/new-adobe-pdf-zero-day-under-attack/…
I would seriously recommend using this instead:
http://www.foxitsoftware.com/pdf/reader/