[cups.general] Can't print bank statement from ar, test page fine.

[Till Kamppeter]

[ Back-posting to the list. ]

Can we then consider "-dPARANOIDSAFER" in GhostScript command lines for
printing as a bug? Should generally only "-dSAFER" be used? Doe this
open security holes like malicious PostScript code reading queued jobs
of other users? Can GhostScript be restricted to only be allowed to read
in the /usr/share/ghostscript/<version>/ tree? Some years ago I have
modified all GhostScript command lines in the Foomatic database to use
"-dPARANOIDSAFER", to improve security. Should I revert this?

Another question: Is it not possible to tell the Acrobat Reader to embed
all fonts in the PostScript output?

   Till


Gene Heskett wrote:
> On Tuesday 22 August 2006 13:03, Till Kamppeter wrote:
>> Try to replace "-dPARANOIDSAFER" by "-dSAFER" in
>> /usr/lib/cups/filter/pstoraster. Does it work then?
>>
>>   Till
>>
> Many Thanks Till, it works normally now.  Even pages are being printed, and 
> the error_log is not being appended to once I set the level back to error.
> 
> What was the reasoning behind that setting as a default?
> 
>> Gene Heskett wrote:
>>> Its setup via the web interface, on /dev/usb/lp0 as a epson c82.
>>> Gutenprint-5.0-rc2.  No  foomatic, I ripped that out several years ago
>>> when I found that gimp-print-4.2.6 didn't need it, and it gave worse
>>> results.  The device URI is  URI: beh:/1/0/30/usb://EPSON/Stylus%20C82
>>>
>>> Up till now, nothings been changed in the setup for months, and
>>> anything I want to print, has just printed, no questions asked.
>>>
>>> And you were right about the -dPARANOIDSAFER, I found a line in the
>>> error logs that confirms it:
>>>
>>> ------------all one line!
>>> D [22/Aug/2006:01:12:38 -0400] [Job 1699] Running /usr/bin/gs -dQUIET
>>> -dDEBUG -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOMEDI
>>> AATTRS -sDEVICE=cups -sstdout=%stderr -sOUTPUTFILE=%stdout -c -
>>> ------------
>>> And above that line in the error_log are indications of
>>>
>>> pstops
>>> pstoraster
>>> rastertogutenprint.5.0
>>> beh
>>>
>>> being called as filters in that order.
>>>
>>> Does this help to locate where I need to edit to fix this?
>