From: Robert Bihlmeyer <robbe@orcus.priv.at>
To: selinux@tycho.nsa.gov
Subject: broad domains
Date: 20 Apr 2003 09:11:46 +0200 [thread overview]
Message-ID: <87n0ilej7x.fsf@orcus.priv.at> (raw)
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
Hi,
I started work on a generic X client domain, but now I get the feeling
that this may not be the right way to go. As I have to add this
permission for this client, and that permission for that program, the
domain gets quite broad. Maybe these generic domains are a mistake?
A have the same problem with the games domain provided in the default
policy (or at least in Russell's package). As is, it doesn't fit half
the stuff in my /usr/games.
On the other hand, having a domain for every teensy toy out there
seems a bit excessive.
Any advice?
BTW, can't setfiles assume some default user & role if none is given?
Repeating system_u:object_r: a million times is superflous.
--
Robbe
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-04-24 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 7:11 Robert Bihlmeyer [this message]
2003-04-24 20:18 ` broad domains Stephen Smalley
2003-04-24 20:18 ` [selinux] " Magosányi Árpád
2003-04-25 3:21 ` Russell Coker
2003-04-27 16:17 ` Robert Bihlmeyer
2003-04-27 17:14 ` Russell Coker
2003-04-27 23:22 ` Brian May
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=87n0ilej7x.fsf@orcus.priv.at \
--to=robbe@orcus.priv.at \
--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.