From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: Joe Nall <joe@nall.com>
Cc: Xavier Toth <txtoth@gmail.com>, SELinux List <selinux@tycho.nsa.gov>
Subject: Re: window manager policy
Date: Mon, 23 Jun 2008 13:18:36 -0400 [thread overview]
Message-ID: <485FDAEC.7010807@tycho.nsa.gov> (raw)
In-Reply-To: <77033ABC-28F3-451A-8400-7AB50FDC929F@nall.com>
Joe Nall wrote:
> On Jun 18, 2008, at 7:20 PM, Eamon Walsh wrote:
>
>
>> Xavier Toth wrote:
>>
>>> I'm contemplating some AVC's that originate in metacity and am
>>> wondering whether a window manager is a special case of an X client
>>> that requires its' own policy. Are there things that a window manager
>>> does that other X clients shouldn't? Also on an MLS system should the
>>> window manager run at the users highwater mark or ranged?
>>>
>>>
>> The window manager basically needs the full run of the display.
>> When another application creates a window, the window manager
>> creates a second window with the titlebar and borders, and then
>> plops the application window down inside of it (reparents it). It
>> also moves windows around and resizes them, sets properties on them
>> (such as the _NET_WM_DESKTOP property that contains the desktop
>> number) and listens for events so it can tell when to change the
>> focus window. Finally, a compositing manager actually needs to read
>> the window contents. It's definitely a special-case app that's
>> going to need its own policy.
>>
>> It almost certainly needs permissions on all windows that map to
>> both read and write in the MLS configuration. So it will need read-
>> and write-all-levels.
>>
>
> What other desktop related processes need MLS policies to be written
> to get a minimally functional Fedora/Gnome enforcing X environment?
>
Don't know for sure...but probably gnome-session (starts up processes),
nautilus and gnome-panel (can be used to launch processes; gnome-panel
interacts with small applet windows that are inside it).
> What window manager/environment do you use in your enforcing X
> development and test?
>
I have one machine where I compile the full Xorg distribution, policy,
and a few other things (pam, gdm) from scratch. I just finished setting
up another machine that runs Fedora 9, with just refpolicy and XCB
compiled from source. This should make it easier for me to develop and
test policy. It's just running regular GNOME, although I may install
XFCE on it as well.
> Do you have a start on a window manager policy that we could try?
>
It should be transitioned into a domain that has unconfined TE perms
over X objects, and is MLS trusted. After that it's a matter of seeing
what permissions regular applications need over window-manager created
windows, particularly decoration windows. They might need some
permissions over the window manager's windows since they might try to
manipulate the window-manager "decoration" windows that their own app
window is reparented into. To deal with this, I think that the window
manager is going to need to call SetWindowCreateContext to put window
decorations into the same context as the associated application window.
I'm hoping to try and make a patch to do this, this week.
--
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:[~2008-06-23 17:18 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 [this message]
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
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=485FDAEC.7010807@tycho.nsa.gov \
--to=ewalsh@tycho.nsa.gov \
--cc=joe@nall.com \
--cc=selinux@tycho.nsa.gov \
--cc=txtoth@gmail.com \
/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.