From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: SELinux List <selinux@tycho.nsa.gov>, Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: What domain should the X server run in
Date: Thu, 25 Oct 2007 15:57:28 -0400 [thread overview]
Message-ID: <4720F528.7030305@tycho.nsa.gov> (raw)
In-Reply-To: <1193338226.9466.148.camel@gorn.columbia.tresys.com>
Christopher J. PeBenito wrote:
> On Thu, 2007-10-25 at 13:27 -0400, Eamon Walsh wrote:
>> The X server runs as xdm_xserver_t if it is started from a display
>> manager. It runs as user_xserver_t if it is started with startx.
>>
>> Is the X server part of the user's session or not?
>>
>> If it is, then it should always run as user_xserver_t, and the display
>> managers should be "fixed" to label the X server with the user's context
>> at login time.
>
> If you're running from [gkx]dm, then the server is running before the
> user has logged in, and not restarted or anything after the user logs
> in, so it stays xdm_xserver_t. Whereas from startx, the user runs it,
> so its a straightforward type_transition to get user_xserver_t. Unless
> the server can be restarted somehow when a user logs in, it seems that
> the only other option would be a dyntransition.
Among other solutions, a text-based or DirectFB-based display manager
could be written that doesn't need X. But I'm going with the single
domain for now.
>
>> It if isn't, then it should always run in the same domain, and
>> startx/xinit should be "fixed" to transition into this context.
>>
>> From my perspective I would favor the latter option for now since it's
>> easier to write policy for. The user's individual windows can be
>> labeled with a per-user type, maintaining separation.
>
> I agree.
>
I tried to go into the xserver module and rip out all the $1_xserver_t
and xdm_xserver_t in favor of just "xserver_t". But, I got bogged down
rather quickly so I gave up on that for now.
--
Eamon Walsh <ewalsh@tycho.nsa.gov>
National Security Agency
--
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:[~2007-10-25 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 17:27 What domain should the X server run in Eamon Walsh
2007-10-25 18:50 ` Christopher J. PeBenito
2007-10-25 19:57 ` Eamon Walsh [this message]
2007-10-26 12:52 ` Russell Coker
2007-10-26 15:43 ` Casey Schaufler
2007-10-26 16:56 ` Russell Coker
2007-10-26 18:15 ` Casey Schaufler
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=4720F528.7030305@tycho.nsa.gov \
--to=ewalsh@tycho.nsa.gov \
--cc=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--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.