Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!apple!ames!nap1!ark1!dsill
From: dsill@ark1.nswc.navy.mil (Dave Sill)
Newsgroups: comp.lang.postscript
Subject: Security of PostScript printers
Message-ID: <133@ark1.nswc.navy.mil>
Date: 20 Sep 89 17:51:17 GMT
Reply-To: dsill@relay.nswc.navy.mil (Dave Sill)
Organization: Naval Surface Warfare Center, Dahlgren, VA
Lines: 17

First let me say I'm not a security weanie, I just want to satisfy my
own curiosity about these issues.  Second, if these have been brought
up before, like in the past couple months, I missed it.  Third, please
don't tell me to RTFM.  I just don't have the time to learn all about
every topic that comes down the pike.

It seems like denying another user the services of a shared PS printer
would be as simple as writing an infinite loop.  On some systems it's
impossible to determine who submitted a given job.

Aren't there ways to change the definition of functions
semipermanently?  Could one write a program that would in some way
alter the output of subsequent jobs?  How about a hack to copy the
next print job to disk?  Surely there's some way to prevent such
things from happening.
-- 
Dave Sill (dsill@relay.nswc.navy.mil)