All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: serial devices
Date: Sat, 4 Oct 2003 14:20:21 +1000	[thread overview]
Message-ID: <200310041420.21903.russell@coker.com.au> (raw)

Currently we have serial ports labeled at tty_device_t by default.

The problem is that serial ports are used for modems, printers, and many other 
things than terminals.  Currently the sample policy does not permit such 
access.  So cups and lpd are not granted access, and if you want to run 
minicom you have to change the context of the device (and add new policy) or 
run minicom as sysadm_t.

I have been thinking of creating a new type for non-login serial devices and 
granting pppd, cups and lpd full access to it, then the administrator would 
have the option of granting users access to it for running minicom without 
allowing them to spoof logins.

Another possibility is to have different types for the device as used by cups, 
pppd, and minicom.  Then change the contexts of serial devices to indicate 
which service they are for, but this could be painful to administer.

What do you think?

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


--
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:[~2003-10-04  4:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04  4:20 Russell Coker [this message]
2003-10-04  8:01 ` serial devices Brian May
2003-10-04 13:12 ` James Morris
  -- strict thread matches above, loose matches on Subject: below --
2007-08-16 13:38 Detlef Spillner
2007-08-16 14:51 ` Kay Sievers

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=200310041420.21903.russell@coker.com.au \
    --to=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.