All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: russell@coker.com.au
Cc: Matt Anderson <mra@hp.com>,
	selinux@tycho.nsa.gov, redhat-lspp@redhat.com
Subject: Re: RFC tweak for lpd.if to make it fit CUPS
Date: Mon, 02 Oct 2006 10:02:24 -0400	[thread overview]
Message-ID: <1159797744.14831.15.camel@sgc> (raw)
In-Reply-To: <200609301423.45245.russell@coker.com.au>

On Sat, 2006-09-30 at 14:23 +1000, Russell Coker wrote:
> On Saturday 30 September 2006 13:54, Matt Anderson <mra@hp.com> wrote:
> > I've been playing around with the printing portion of the policy a bit
> > and would like to suggest some changes.  Looking at the source for
> > lpd.if it seems the the policy was originally written with a lpr/lpd in
> > mind that is not CUPS.
> 
> Correct.  The lpr/lpd policy was written a long time before the cups policy.  
> My recollection is that I wrote the cups policy to support mixed-mode systems 
> with lpr/lpd emulation in CUPS and easy conversion between cups and lpd.
> 
> For today's use it's probably best to just dump support for lpd.  In Fedora 
> cups is the only supported option, for LSPP you have the same but no option 
> of getting lprng from extras, in Debian things are tending towards cups (and 
> with Debian having more support for modules we can probably switch between 
> cups and lpd modules).

Seems that we're going to have to split lpr out again, and turn it into
a mta-like setup.

> > There are comments referencing a lightweight 
> > mode, and $1_lpr_t is allowed to read and write to the spool directly.
> > CUPS does not do these things.  Attached is a patch I've applied to my
> > systems that allows CUPS to work just fine in Targeted and MLS mode with
> > 13 less allow rules.
> 
> That seems fine to me.

If we split out lpr, then we can make all the rules optional on lpd or
cups, depending on what is installed.  I'd rather not remove the rules
completely unless we can confirm it doesn't need these rules, otherwise
lpd support may break.

-- 
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

      reply	other threads:[~2006-10-02 14:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-30  3:54 RFC tweak for lpd.if to make it fit CUPS Matt Anderson
2006-09-30  4:23 ` Russell Coker
2006-10-02 14:02   ` Christopher J. PeBenito [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1159797744.14831.15.camel@sgc \
    --to=cpebenito@tresys.com \
    --cc=mra@hp.com \
    --cc=redhat-lspp@redhat.com \
    --cc=russell@coker.com.au \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.