> From [EMAIL PROTECTED] Fri Feb 15 08:21:26 2002
> Date: Fri, 15 Feb 2002 10:32:13 -0500 (EST)
> From: "William R. Knox" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Subject: Re: LPRng: running lprng as non-root user
>
> The client parts of LPRng are often installed setuid root so that they can
> send from a privileged port (something in the RFC states that requests
> need to be issued from the range 721-731 - most lpd servers do not enforce
> that, but that's why the client would be installed as root).
>
>                       Bill Knox
>                       Senior Operating Systems Programmer/Analyst
>                       The MITRE Corporation
>

Umm... except for Solars, HP JetDirect, HP-UX, etc. etc. etc.

I stronly recommend that you do NOT install the clients setuid,
and at one point set the default configuration for this.

A slew of users who wanted to spool directly to Non-LPRng systems
reported the problems...  So I backed out the change.

Apparently at the time 'security' took (and still takes) a back seat
to 'ease of use'.

Patrick ("Microsoft got religion - but their Lent is only 30 days,
   they don't promise to reform,  and then it is business as
   normal.  Sounds awfully like my lifestyle."
     (anonymous and very funny comment from BSDCon 2002)

   ) Powell

-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to