Re: possible issue with ps2pdf (9.25) and transparency

Hello,

I am against the idea that any non-standard PostScript extension
should "just work" by default in Ghostscript, cf. the section
"Security: Make Things Not Just Work" in
https://en.opensuse.org/SDB:CUPS_and_SANE_Firewall_settings

On Sep 15 19:43 Ken Sharp wrote (excerpt):
> If you want to use non-standard PostScript extensions,
> then you can't use SAFER,
> this doesn't seem unreasonable to me.

I think that by default any PostScript interpreter
(in particular Ghostscript) should not support
anything that is not standard PostScript.

I assume currently this is not possible but I would appreciate it
when in a future Ghostscript version any non-standard PostScript
extension would only be supported when a special command line
option was explicitly specified that enables the extension.

Such a special command line option would be different
from what '-dSAFER' is intended to do.

Because standard PostScript supports arbitrary file access
on the system disk via standard PostScript operators like
'file', 'readstring', 'writestring', ... and 'closefile'
a special command line option like '-dSAFER' is needed
to make Ghostscript "safer" than standard PostScript.

See the subsection
"Other parameters" in "Command line options" in
https://ghostscript.com/doc/9.25/Use.htm
how '-dSAFER' is intended to limit file access.


Kind Regards
Johannes Meixner
-- 
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)