All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Anderson <mra@hp.com>
To: selinux@tycho.nsa.gov, redhat-lspp@redhat.com
Subject: New MLS constraint?
Date: Mon, 16 Oct 2006 12:40:46 -0400	[thread overview]
Message-ID: <4533B60E.8010802@hp.com> (raw)

With the removal of TCS's dev-allocator the solution for multi-level
printers that came out of the LSPP calls was to set a range on the
printer device, using chcon, and use SELinux to verify that the print
job was inside that range.

I've since added checking code to the server which does not allow jobs
to be enqueued into the spool or queued and printed unless an
avc_has_perm() check passes.  The current check uses SECCLASS_FILE, and
checks FILE__WRITE;

The subject is something like user_u:user_r:user_lpr_t:s2:A
The object is: system_u:object_r:printer_device_t:s2-s15:c0.c1023

When I do this check however, I get denied whenever the user's context
does not equal the lower level.  Is there a constraint that I can apply,
preferably to the object's type (printer_device_t as opposed to *_lpr_t,
) that would allow the above check to succeed?

-matt

--
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-16 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 16:40 Matt Anderson [this message]
2006-10-16 17:47 ` New MLS constraint? Christopher J. PeBenito
2006-10-16 18:53   ` Matt Anderson
2006-11-01  0:47   ` Matt Anderson
2006-11-01 15:41     ` Christopher J. PeBenito

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=4533B60E.8010802@hp.com \
    --to=mra@hp.com \
    --cc=redhat-lspp@redhat.com \
    --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.