All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: Ted X Toth <txtoth@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: XACE and MLS
Date: Tue, 05 Dec 2006 18:37:41 -0500	[thread overview]
Message-ID: <457602C5.9050504@tycho.nsa.gov> (raw)
In-Reply-To: <4575F6E9.1020600@gmail.com>

Ted X Toth wrote:
> We are interested in using X and an associated desktop/window manager 
> (most likely GNOME/Metacity) in an MLS environment and I'm trying to 
> figure out what all needs to be addressed to get there. A couple of 
> areas that I've thought about so far are window labeling and cut and 
> paste. For window labeling the window manager ought to be able to use 
> the context of it X server connection to decorate the window with the 
> level but what happens if for example a user does a newrole and changes 
> their level? 

The XSELinux extension provides window properties that can be used by 
the window manager in the same manner as the usual WM_NAME, WM_COMMAND, 
etc.  The one currently available is _SELINUX_CLIENT_CONTEXT which 
contains the domain of the connected process.  Others will be introduced 
in the future in particular _SELINUX_CONTEXT which will contain the 
context of the window itself.

Here's a screen shot of a hacked twm that displays this property in 
place of the usual window title:
http://people.freedesktop.org/~ewalsh/twm-demo.png

Note that what's really needed for proper labeling however is a 
server-controlled, secure area of the screen that clients can't draw 
into.  There could be spoofing attacks otherwise.

> For cut and paste dominance checks are needed would it be 
> reasonable to do these as an extension of the XACE and if so where can I 
> find out more about how to do this and if not where then?

It depends on which cut & paste.  The X server provides two methods: cut 
buffers, which are implemented as properties on the root window, and 
selections, which are implemented using a convoluted method of setting 
properties on client windows and sending notification events.  I believe 
that both of these methods should be securable using the XSELinux 
extension although ths work has not been done just yet.

Other cut & paste functionality may be provided by higher-level layers 
such as toolkits (GTK+) or desktop systems (GNOME, etc).  I have no 
knowledge of these areas.

A good reference for X cut & paste is the xlib.PS document in the 
xorg-docs package.  The basic SELinux X classes and permissions are 
described in the "Securing the X Window System with SELinux" paper on 
www.nsa.gov/selinux.

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

      reply	other threads:[~2006-12-05 23:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 19:11 [PATCH] refpolicy: add X object classes to unconfined_t Eamon Walsh
2006-09-13 13:47 ` Christopher J. PeBenito
2006-09-13 21:13   ` Eamon Walsh
2006-09-14 14:10 ` Joshua Brindle
2006-09-15 12:46   ` Joshua Brindle
2006-09-15 21:19     ` Eamon Walsh
2006-09-18 14:43       ` Christopher J. PeBenito
2006-11-29 15:12       ` Xavier Toth
2006-11-29 20:09         ` Eamon Walsh
2006-11-29 22:34           ` Xavier Toth
2006-11-30  3:27             ` Eamon Walsh
2006-12-05 22:47               ` XACE and MLS Ted X Toth
2006-12-05 23:37                 ` Eamon Walsh [this message]

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=457602C5.9050504@tycho.nsa.gov \
    --to=ewalsh@tycho.nsa.gov \
    --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.