Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.postscript > #3399

Re: gslp -- ghostscript line printer -- to emulate enscript

Show all headers | View raw

In article <ca56718b-f096-4308-a8ec-49472426ebc2@googlegroups.com>, 
dougLas.L.mcaLLaster.civ@mail.mil says...

> This script crashes:

Actually no, from later in your post it doesn't crash, ti gives you an 
error, that's not the same thing at all (unless there is also a crash 
which you didn't mention).

 
> gslp myfile.txt
> 
> Can some kind soul help me get it working?

I suppose my first question would be 'what did you expect this to do ?'

Reading the bash script, it appears to invoke Ghostscript to run the 
gslp.ps program, and to send the output via an Espon device driver. It 
doesn't seem to set an output file so unless you set one at the command 
line (which you haven't done) it will simply throw an error.


> Here is what is returned:
> 
> error: /invalidfileacces in --file--
> operand stack:
>  --nostringval-- (myfile.txt) (r)
> more unintelligible stuff

I don't want to seem picky, but it would really help if you actually 
posted the *whole* back channel outptu, including the 'unintelligible 
stuff'. It may be unintelligible to you, but not to me.

 
> I tried both with and without full path -- same crash.

OK this is not a crash, its a graceful exit due to an error condition.

I've never seen this script before, and I quesiton its actual utility, 
but the problem is simply that it sets -dSAFER, which is a problem, 
because that prevents access to random files by PostScript programs 
(gslp.ps is a PostScript program).

Recent versions of Ghostscript have tightened up considerably on the use 
of SAFER and the 'invalidfileacccess' error means simeply that it was 
invalid to attempt to access the given file under the current 
conditions.

Your only solution is to edit the gslp script and remove the -dSAFER 
from it. Since you are running a PostScript program supplied with 
Ghostscript, and that program doesn't execute random PostScript 
programs, this is safe.

Though I would very much recommend that you upgrade to a newer verison 
of Ghostscript. The version you are using is 3 years old and has known 
security vulnerabilities.

Oh, you will also need to supply -sOutputFile=<insert name of output 
file> on the gslp command line, or you'll simply get a different error.

			Ken

Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

gslp -- ghostscript line printer -- to emulate enscript dm <dougLas.L.mcaLLaster.civ@mail.mil> - 2019-05-21 23:11 -0700
  Re: gslp -- ghostscript line printer -- to emulate enscript ken <ken@spamcop.net> - 2019-05-22 09:17 +0100
    Re: gslp -- ghostscript line printer -- to emulate enscript dm <dougLas.L.mcaLLaster.civ@mail.mil> - 2019-05-22 16:44 -0700
      Re: gslp -- ghostscript line printer -- to emulate enscript luser droog <luser.droog@gmail.com> - 2019-05-22 17:11 -0700
        Re: gslp -- ghostscript line printer -- to emulate enscript John Forkosh <forkosh@panix.com> - 2019-05-23 04:35 +0000

csiph-web