Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uwm.edu!linac!att!cbnewsh!gls
From: gls@corona.ATT.COM
Newsgroups: comp.bugs.sys5
Subject: Re: security in lp(1)
Keywords: sort bug
Message-ID: <1991Apr13.195523.21043@cbnewsh.att.com>
Date: 13 Apr 91 19:55:23 GMT
Article-I.D.: cbnewsh.1991Apr13.195523.21043
References: <1991Apr11.031926.19901@cs.uow.edu.au> <1950@ahds.UUCP>
Sender: gls@cbnewsh.att.com (Col. G. L. Sicherman)
Organization: AT&T Bell Laboratories
Lines: 16

Don't be afraid to hack the lp code, or even to write your own version
of lpsched.  That's what UNIX(R) is all about -- writing your own
programs and tweaking the distributed source code.

In the meantime, you can print private files with

	lp < myfile
or
	for FILE in myfile*; do lp < $FILE; done

You can even write your own "lp" script or alias that inserts the "<"
before running /usr/bin/lp.  The only difficulty is that the name of the
file won't appear on the banner page.
-- 
Col. G. L. Sicherman
gls@corona.att.COM