All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted X Toth <txtoth@gmail.com>
To: Eamon Walsh <ewalsh@tycho.nsa.gov>
Cc: Joe Nall <joe@nall.com>, SELinux List <selinux@tycho.nsa.gov>
Subject: Re: window manager policy
Date: Sat, 28 Jun 2008 09:29:40 -0500	[thread overview]
Message-ID: <48664AD4.1010904@gmail.com> (raw)
In-Reply-To: <4865AED6.9020404@tycho.nsa.gov>

Eamon Walsh wrote:
> Joe Nall wrote:
>>
>> What other desktop related processes need MLS policies to be written  
>> to get a minimally functional Fedora/Gnome enforcing X environment?
>>
>> What window manager/environment do you use in your enforcing X  
>> development and test?
>>   
>
> Many AVC's I'm getting are caused by the fact that the server starts 
> up as xdm_xserver_t:
>
> allow sysadm_t xdm_rootwindow_t:x_colormap { use install uninstall };
> allow sysadm_t xdm_rootwindow_t:x_drawable { get_property show read 
> manage add_child remove_child list_child hide setattr receive 
> set_property create send write
> allow sysadm_t xdm_xserver_t:x_device { setfocus use setattr grab 
> manage getattr freeze };
> allow sysadm_t xdm_xserver_t:x_screen { saver_setattr saver_getattr 
> setattr };
> allow sysadm_t xdm_xserver_t:x_server manage;
>
>
> ...and xdm_t windows are apparently still open on the display when the 
> user's gnome-session is run:
>
> allow sysadm_t xdm_t:x_client destroy;
> allow sysadm_t xdm_t:x_drawable { get_property receive getattr 
> list_child };
> allow sysadm_t xdm_xproperty_t:x_property { write read };
>
>
>
> This week I attempted to write a prototype display manager that would 
> stop the X server and run a new one after the user logs in.  However 
> this process looks incredibly ugly and takes forever, and I'm also 
> having trouble with the X server not starting up at all some of the 
> time, so I've given up on that for now.
>
> I did get a patch into gdm this week though.  

What does the gdm mod do, restart the X server as the user?
> Once libxcb-selinux is released I'll be able to make patch for PAM to 
> have it relabel X server objects dynamically as part of pam_open_session.
>
> I'll take a look at the window manager policy next week.
>


--
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.

  parent reply	other threads:[~2008-06-28 14:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 21:01 window manager policy Xavier Toth
2008-06-19  0:20 ` Eamon Walsh
2008-06-19 21:23   ` Joe Nall
2008-06-19 23:12   ` Joe Nall
2008-06-20  9:50     ` Russell Coker
2008-06-23 17:18     ` Eamon Walsh
2008-06-23 18:23       ` Xavier Toth
2008-06-23 19:03         ` Eamon Walsh
2008-06-25 19:20       ` Xavier Toth
2008-06-28  3:24     ` Eamon Walsh
2008-06-28  3:47       ` Joe Nall
2008-06-28 14:29       ` Ted X Toth [this message]
2008-07-03 20:09         ` Eamon Walsh

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=48664AD4.1010904@gmail.com \
    --to=txtoth@gmail.com \
    --cc=ewalsh@tycho.nsa.gov \
    --cc=joe@nall.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.