home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.postscript
- Path: sparky!uunet!ukma!usenet.ins.cwru.edu!agate!ames!purdue!mentor.cc.purdue.edu!news
- From: ab@nova.cc.purdue.edu (Allen B)
- Subject: Re: Postscript considered harmful with MIME
- Message-ID: <C1KKz0.Lsq@mentor.cc.purdue.edu>
- Sender: news@mentor.cc.purdue.edu (USENET News)
- Organization: Purdue University
- References: <1993Jan28.001842.25259@aio.jsc.nasa.gov>
- Date: Thu, 28 Jan 1993 15:13:48 GMT
- Lines: 22
-
- In article <1993Jan28.001842.25259@aio.jsc.nasa.gov>
- kjenks@gothamcity.jsc.nasa.gov writes:
- > PostScript is really a general-purpose programming language. It's
- > difficult to work with, especially if you wanted to make it do disk
- > I/O, but a really creative virus vandal could conceivably cause
- > GhostScript (or some other PostScript interpretter running in your CPU)
- > to create a script file in your home directory called, say, "ls" which
- > does an "rm -r * > /dev/null" or some such nasty.
-
- No, actually, it's really easy.
-
- (*) {
- deletefile
- } filenameforall
-
- is the code you describe, I think.
-
- Low-level file operations in PostScript are nearly the
- same difficulty as they are in C. High level ones are even
- easier, as my example shows.
-
- Allen B (Who uses files from PostScript)
-