From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: successful cupsys admin: advantages of running pam_selinux
Date: Sun, 6 Jun 2004 00:08:53 +0000 [thread overview]
Message-ID: <20040606000852.GA6673@lkcl.net> (raw)
it is with some amazement that, by adding pam_selinux to /etc/pam.d/cups
and by adding an ordinary user to the lpadmin group that i was able
to have that ordinary user set up a local printer and actually print
to it (openoffice).
i am aware that there are concerns about pam_selinux being inappropriate
for certain things - openssh being one of them due to ttys not being
managed properly, and kdm when you set AutoLogin is another.
however the prospect of having to code up a policy for doing what i
just managed to do fills me with some trepidation.
i could not tell you where to begin to get the same effect as the
lpadmin group.
six of one, half a dozen of the other.
i mention all this just in case someone thought "i know, pam_selinux
is bad, let's drop it entirely".
l.
--
--
expecting email to be received and understood is a bit like
picking up the telephone and immediately dialing without
checking for a dial-tone; speaking immediately without listening
for either an answer or ring-tone; hanging up immediately and
believing that you have actually started a conversation.
--
<a href="http://lkcl.net"> lkcl.net </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />
--
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.
next reply other threads:[~2004-06-06 0:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 0:08 Luke Kenneth Casson Leighton [this message]
2004-06-06 9:46 ` successful cupsys admin: advantages of running pam_selinux Russell Coker
2004-06-06 10:22 ` Luke Kenneth Casson Leighton
2004-06-06 11:05 ` Luke Kenneth Casson Leighton
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=20040606000852.GA6673@lkcl.net \
--to=lkcl@lkcl.net \
--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.