All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: Joe Nall <joe@nall.com>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
	Adam Jackson <ajax@redhat.com>,
	SELinux List <selinux@tycho.nsa.gov>
Subject: Re: Permissive mode for xace is broken.
Date: Tue, 26 Feb 2008 22:46:48 -0500	[thread overview]
Message-ID: <47C4DD28.90805@tycho.nsa.gov> (raw)
In-Reply-To: <FD5B0C7C-60A9-46F4-8986-A8EB31BABDC8@nall.com>

[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]

Joe Nall wrote:
> On Feb 26, 2008, at 8:31 PM, Eamon Walsh wrote:
>   
>> I found the source of the BadWindow errors.  I'm going to fix this  
>> upstream and throw an SRPM patch to Dan so he can test.
>>
>> Also, I think I'm going to change XQueryPointer() from requring  
>> "read" to simply "getattr" permission on the device.  I really do  
>> think it should require "read," but too many things call it and we  
>> need to turn "read" off to prevent the xspy attack.
>>
>> Finally, I'm going to try and get the polyinstantiation code for  
>> properties and selections in before the feature freeze.
>>     
>
> Awesome. Can I get a copy of the patch too?
>
> joe
>   

Attached and selinux list cc'ed.

One more thing: the SELinux extension is part of extmod, so you can do 
this in your xorg.conf if you want to disable it:

Section "Module"
        SubSection "extmod"
		Option "omit SELinux"
        EndSubSection
EndSection


At the present time there is no enforcing/permissive switch for just the 
xserver.


-- 
Eamon Walsh <ewalsh@tycho.nsa.gov>
National Security Agency


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: badwindow_fix.patch --]
[-- Type: text/x-patch; name="badwindow_fix.patch", Size: 0 bytes --]



  parent reply	other threads:[~2008-02-27  3:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 14:09 Permissive mode for xace is broken Daniel J Walsh
2008-02-25 14:12 ` Stephen Smalley
2008-02-25 14:24   ` Stephen Smalley
2008-02-25 14:48     ` Daniel J Walsh
2008-02-25 18:49       ` Stephen Smalley
2008-02-25 19:28         ` Daniel J Walsh
2008-02-25 20:12           ` Daniel J Walsh
2008-02-25 22:04             ` Eamon Walsh
2008-02-25 20:33           ` Eamon Walsh
2008-02-26  1:12             ` Eamon Walsh
2008-02-26 12:59               ` Stephen Smalley
2008-02-26 13:09                 ` Daniel J Walsh
2008-02-27  2:31                   ` Eamon Walsh
     [not found]                     ` <FD5B0C7C-60A9-46F4-8986-A8EB31BABDC8@nall.com>
2008-02-27  3:46                       ` Eamon Walsh [this message]
2008-02-28 18:48                 ` Eamon Walsh
2008-02-28 18:51                   ` Stephen Smalley
2008-02-28 19:00                     ` Daniel J Walsh
2008-02-28 21:17                     ` Steve Grubb
2008-02-28 21:34                       ` Daniel J Walsh
2008-02-29  1:58                       ` Eamon Walsh
2008-02-29  2:02                       ` Eamon Walsh
2008-03-17 20:11                         ` Steve Grubb
2008-03-20  3:56                           ` Eamon Walsh
2008-02-26 14:34               ` Daniel J Walsh
  -- strict thread matches above, loose matches on Subject: below --
2008-03-24 15:55 Steve G
2008-03-24 19:59 ` Stephen Smalley
2008-03-24 20:28   ` Steve Grubb
2008-03-27 20:08 ` 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=47C4DD28.90805@tycho.nsa.gov \
    --to=ewalsh@tycho.nsa.gov \
    --cc=ajax@redhat.com \
    --cc=dwalsh@redhat.com \
    --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.