On Sat, 18 Apr 1998, Pete Durst wrote:
> It appears that these files do not yet exist.  Will they be up soon?
> 
> >A major security problem has been found in all versions of lpr shipped with
> >Red Hat Linux. Version 0.30 of lpr fixes this and is now available from

...

But the daemon still bombs if you type "lpr -c /etc/printcap". Boom.
Looking at file "printjob.c" it becomes obvious -- it's trying to execute
a NULL pointer as the arg to execve (to run the print filter). The fix is
also obvious -- do something besides bomb when you have a NULL print
filter. The BSD folks make it send a message to syslog that they're trying
to run an illegal filter, while I personally just go ahead and print the
dadburned thing (i.e. jump back to the "dump data to stdout" code). 

Not that this is a show-stopper, but it is disconcerting, especially when
you have people who came from SCO Unix who use "-c" by habit (under Sys V
it means "make a copy of the file instead of a link to the file", and is
needed when the 'lp' daemon does not have access to the directory the file
is in -- the usual case in my development environment, because nobody and
nothing besides the developers have access to our source code
directories). 

Eric Lee Green   [EMAIL PROTECTED]          Executive Consultants
Systems Specialist               Educational Administration Solutions
 "We believe Windows 95 is a walking antitrust violation" -- Bryan Sparks


-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to