From: Russell Coker <russell@coker.com.au>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: ivg2@cornell.edu, selinux@tycho.nsa.gov
Subject: Re: [ PATCH ] X clients cleanup Patch #3
Date: Sat, 2 Apr 2005 22:27:38 +1000 [thread overview]
Message-ID: <200504022227.40688.russell@coker.com.au> (raw)
In-Reply-To: <424E8A49.2090408@redhat.com>
On Saturday 02 April 2005 22:04, Daniel J Walsh <dwalsh@redhat.com> wrote:
> Do we want to remove tmpfs_domain from base_user_domain. I would prever
> to have policy where X privs for users is optional.
> Think eventually about loadable modules, where you have a X user support
> module. Server users need a lot less privs.
When you say "X is optional" do you mean to have a boolean or to have it
optional at compile time?
If a boolean then we would probably have the boolean not stop tmpfs access.
If optional at compile time then we certainly want tmpfs_domain in
base_user_domain.
I think that in any case we probably want tmpfs_domain in base_user_domain
just for best structure of policy.
--
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:[~2005-04-02 12:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 22:28 Further X client cleanups..questions Ivan Gyurdiev
2005-03-31 22:34 ` Ivan Gyurdiev
2005-04-02 4:31 ` [ PATCH ] X clients cleanup Patch #3 Ivan Gyurdiev
2005-04-02 12:04 ` Daniel J Walsh
2005-04-02 12:27 ` Russell Coker [this message]
2005-04-02 15:43 ` Ivan Gyurdiev
[not found] ` <425154AB.8080206@redhat.com>
2005-04-05 22:56 ` Ivan Gyurdiev
2005-04-06 4:18 ` Ivan Gyurdiev
2005-04-06 4:41 ` Ivan Gyurdiev
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=200504022227.40688.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=dwalsh@redhat.com \
--cc=ivg2@cornell.edu \
--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.