Bug#618530: ghostscript: cannot open OutputFile if -dSAFER specified with piped or interactive input
Package: ghostscript
Version: 8.71~dfsg2-9
Severity: normal
The behavior of the -dSAFER flag has changed between versions of Ghostscript
in Lenny and Squeeze. It now prevents -sOutputFile from working if the
input is taken interactively or from a pipe. For example:
user@host:path$ gs -q -dSAFER -dSAFINTERPOLATE -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -sDEVICE=ppmraw -r144 -sOutputFile=foo.ppm
GS>(foo.ps) run
Error: /invalidfileaccess in --run--
Operand stack:
(foo.ps) (r)
...
This is annoying for those of us who use pipes in scripts to generate graphics,
say for web applications. Google did not show any obvious accounts of this.
At the very least, it should be documented in a changelog.
-- System Information:
Debian Release: 6.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ghostscript depends on:
ii debconf [de 1.5.36.1 Debian configuration management sy
ii debianutils 3.4 Miscellaneous utilities specific t
ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2 Fonts for the Ghostscript interpre
ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib
ii libgs8 8.71~dfsg2-9 The Ghostscript PostScript/PDF int
ghostscript recommends no packages.
ghostscript suggests no packages.
-- no debconf information
Reply to: