Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Nov 2000 21:00:03 -0800 (PST)
From:      Garance A Drosihn <drosih@rpi.edu>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: bin/7973: lpd: Bad control file owner in case of remote printing
Message-ID:  <200011030500.VAA29280@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/7973; it has been noted by GNATS.

From: Garance A Drosihn <drosih@rpi.edu>
To: freebsd-gnats-submit@FreeBSD.org
Cc: cejkar@dcse.fee.vutbr.cz
Subject: Re: bin/7973: lpd: Bad control file owner in case of remote
 printing
Date: Thu, 2 Nov 2000 23:55:11 -0500

 Rudolf Cejka wrote:
 
 >   Problem is with /var/spool/lpd/*/cf* control files. If file is
 >   printed locally (via lpr), cf* file is created with right
 >   permissions:
 >       ls -l =>    -rw-rw---- 1 daemon daemon ... cf*.
 >   But if file is printed remotely and cf* are creates by lpd,
 >   cf* files have bad permissions:
 >       ls -l =>    -rw-rw---- 1 root daemon ... cf*.
 >
 >   It has bad impact on print filters ("if" in printcap) which
 >   extract some information from cf* control files. Filters
 >   are executed with these ids: uid=1 (daemon) gid=0 (wheel).
 >   They do not belong to wheel group.
 
 I understand the issue you are talking about, but I would argue
 that print filters have no business reading the control files.
 The control files are "a protocol" of sorts for an lpr process
 (or some other lpd process) to communicate with an lpd process.
 
 Imagine what happens if we want to change the format of cf
 files, which we may very well want to do (if we accept jobs
 from via protocols other than lpd).  I don't think print
 filters should have any idea of the format of cf files.
 
 So, my question to you is, What is the exact information that
 your print filters need from the cf-files?  For your print
 filters, would it be better if they picked up that information
 (whatever you need) via some environment variables that lpd
 might set before starting up your filter?
 
 This is the solution I would prefer to implement.
 -- 
 
 ---
 Garance Alistair Drosehn            =   gad@eclipse.acs.rpi.edu
 Senior Systems Programmer           or  gad@freebsd.org
 Rensselaer Polytechnic Institute    or  drosih@rpi.edu
 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011030500.VAA29280>