From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Valdis.Kletnieks@vt.edu
Cc: Stephen Smalley <sds@epoch.ncsc.mil>, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: [idea] multiple contexts.
Date: Tue, 27 Jul 2004 22:28:36 +0100 [thread overview]
Message-ID: <20040727212836.GA21236@lkcl.net> (raw)
In-Reply-To: <200407271940.i6RJebSp032388@turing-police.cc.vt.edu>
On Tue, Jul 27, 2004 at 03:40:37PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 27 Jul 2004 17:06:06 BST, Luke Kenneth Casson Leighton said:
>
> > i also seek to limit the programs that a KDE user may run.
> >
> > if there is a simple way to do that which does not involve writing
> > policy files for each and every single KDE program i intend to restrict
> > users to use, i would be interested to hear it.
>
> Are there KDE programs that don't require anything but user permissions, but
> that you want to restrict anyhow?
yes, sort-of: more that i only wish to limit what programs a user
can run (and what programs _those_ programs can run).
in particular, i want to stop people from being able to use the
"Run" capability of Konqueror, etc. STOP, not have the popup coming
up with "are you sure you want to run this program?".
setting up a kdeusers group, chgrp'ing the allowed programs
to that group, and setting permissions to 0660 is what i really
need...
... but i wondered if there was a way to do that same thing in
SE/Linux...
... _without_ writing a whole stack of policies, one per program.
a macro i could write that would let me do this:
allow_user_kde_access(konqueror_exec_t)
allow_user_kde_access(k3b_exec_t)
with all that that implies.
or, to simply set all the allowed kde executables into
kde_user_exec_t type, and set this on /usr/bin/konqueror,
/usr/bin/k3b, /usr/bin/koffice etc.
l.
--
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 prev parent reply other threads:[~2004-07-27 21:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 23:11 [idea] multiple contexts Luke Kenneth Casson Leighton
2004-07-25 0:17 ` Russell Coker
2004-07-26 16:12 ` Stephen Smalley
2004-07-27 16:06 ` Luke Kenneth Casson Leighton
2004-07-27 17:33 ` Stephen Smalley
2004-07-27 18:23 ` Luke Kenneth Casson Leighton
2004-07-28 23:16 ` Erich Schubert
2004-07-29 1:00 ` Luke Kenneth Casson Leighton
2004-07-27 19:40 ` Valdis.Kletnieks
2004-07-27 21:28 ` Luke Kenneth Casson Leighton [this message]
2004-07-27 21:23 ` Valdis.Kletnieks
2004-07-27 21:49 ` Luke Kenneth Casson Leighton
2004-07-28 12:33 ` David Caplan
2004-07-28 14:37 ` 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=20040727212836.GA21236@lkcl.net \
--to=lkcl@lkcl.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=sds@epoch.ncsc.mil \
--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.