All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE-Linux <selinux@tycho.nsa.gov>, tresys <refpolicy@oss1.tresys.com>
Subject: Re: opensuse and SELinux = some dbus roblem with xdm/gdm
Date: Wed, 09 Sep 2009 07:51:01 -0700	[thread overview]
Message-ID: <4AA7C0D5.3090706@gmail.com> (raw)
In-Reply-To: <1252500902.13634.647.camel@moss-pluto.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Tue, 2009-09-08 at 22:33 -0700, Justin P. Mattock wrote:
>    
>> Justin Mattock wrote:
>>      
>>> Not sure if this is SELinux/refpolicy
>>>
>>> Out of curiosity I wanted to setup the latest
>>> policy with the latest opensuse.
>>> Seems everything has gone o.k. for the moment.
>>>
>>> The proble Im running into is xdm/gdm seems to crap out
>>> with some dbus error message:
>>>
>>> ** (gdm:1566): WARNING **: Couldn't connect to system bus: An SELinux
>>> policy prevents this sender from sending this message to this recipient
>>> (rejected message had sender "(unset)" interface "freedesktop.DBus"
>>> member "Hello"
>>> error name "(unset)" destination "org.freedesktop.DBus")
>>>
>>> The funny thing with this is with the initial policy load
>>> I hadn't relabeled yet, and the system had loaded the policy
>>> just fine and xdm worked then once I relabeled this appeared and xdm/gdm
>>> just craps out.(the policy is all in permissive mode, giving selinux=0
>>> makes the system operate as should).
>>>
>>> Also not sure if this matters but in
>>> /etc/pam.d{gdm,login,xdm) I added
>>> pam_selinux.so open/close but had no idea
>>> where they should be placed.
>>>
>>> Any ideas?
>>>
>>>
>>>        
>> Shoot I didn't look, but when I do a
>> ldd /usr/sbin/gdm I see nothing with libselinux nor
>> libaudit.
>>
>> loading an ubuntu livecd results in showing
>> libselinux.
>>
>> my guess since this is a development version they haven't
>> enabled SELinux support yet with gdm.
>>
>> ohh well, I guess Ill leave it at that.
>>      
>
> The gdm selinux support was obsoleted by the gdm rewrite, so it isn't
> necessary to link it with libselinux anymore.  It all gets handled by
> pam_selinux in /etc/pam.d/gdm.  In Fedora, /etc/pam.d/gdm looks like
> this:
> #%PAM-1.0
> auth     [success=done ignore=ignore default=bad] pam_selinux_permit.so
> auth       required    pam_succeed_if.so user != root quiet
> auth       required    pam_env.so
> auth       substack    system-auth
> auth       optional    pam_gnome_keyring.so
> account    required    pam_nologin.so
> account    include     system-auth
> password   include     system-auth
> session    required    pam_selinux.so close
> session    required    pam_loginuid.so
> session    optional    pam_console.so
> session    required    pam_selinux.so open
> session    optional    pam_keyinit.so force revoke
> session    required    pam_namespace.so
> session    optional    pam_gnome_keyring.so auto_start
> session    include     system-auth
>
> BTW, I would recommend testing the policy package provided by OpenSUSE
> to see if it works before trying upstream refpolicy.
>
> And report issues with their SELinux integration to their bugzilla, not
> to us.  It won't get fixed if you just post it here.
>
> Are you following the guidance at:
> http://en.opensuse.org/SELinux
>
> You have to add an additional repository to pick up their policy and associated packages.
>
> The SELinux integration work seems to be getting tracked on this blog:
> http://thetoms-random-thoughts.blogspot.com/search/label/Security
>
>    
So your telling me you can compile this
package without the audit/selinux switches,
and still run a policy?

doing a ldd /usr/sbin/gdm
shows nothing with libpam(ubuntu does).

As of now everything is opensused out
did have userspace put in, but was easily
written over by suse. Ill try
your gdm config for pam.d but Im just not
connecting the dots on this. FWIW heres what
ldd /usr/sbin/gdm  has for the libs.

linux-vdso.so.1
libXau.so.6
libdbus-glib-1.so.2
libgobject-2.0.so.0
libglib-2.0.so.0
libdbus-1.so.3
libpthread.so.0
libXdmcp.so.6
libwrap.so.0
libc.so.6
libpcre.so.0
librt.so.1
ld-linux-x86-64.so.2

I suppose I have to reinstall to get things in order.

Justin P. Mattock

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

WARNING: multiple messages have this Message-ID (diff)
From: justinmattock@gmail.com (Justin P. Mattock)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] opensuse and SELinux = some dbus roblem with xdm/gdm
Date: Wed, 09 Sep 2009 07:51:01 -0700	[thread overview]
Message-ID: <4AA7C0D5.3090706@gmail.com> (raw)
In-Reply-To: <1252500902.13634.647.camel@moss-pluto.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Tue, 2009-09-08 at 22:33 -0700, Justin P. Mattock wrote:
>    
>> Justin Mattock wrote:
>>      
>>> Not sure if this is SELinux/refpolicy
>>>
>>> Out of curiosity I wanted to setup the latest
>>> policy with the latest opensuse.
>>> Seems everything has gone o.k. for the moment.
>>>
>>> The proble Im running into is xdm/gdm seems to crap out
>>> with some dbus error message:
>>>
>>> ** (gdm:1566): WARNING **: Couldn't connect to system bus: An SELinux
>>> policy prevents this sender from sending this message to this recipient
>>> (rejected message had sender "(unset)" interface "freedesktop.DBus"
>>> member "Hello"
>>> error name "(unset)" destination "org.freedesktop.DBus")
>>>
>>> The funny thing with this is with the initial policy load
>>> I hadn't relabeled yet, and the system had loaded the policy
>>> just fine and xdm worked then once I relabeled this appeared and xdm/gdm
>>> just craps out.(the policy is all in permissive mode, giving selinux=0
>>> makes the system operate as should).
>>>
>>> Also not sure if this matters but in
>>> /etc/pam.d{gdm,login,xdm) I added
>>> pam_selinux.so open/close but had no idea
>>> where they should be placed.
>>>
>>> Any ideas?
>>>
>>>
>>>        
>> Shoot I didn't look, but when I do a
>> ldd /usr/sbin/gdm I see nothing with libselinux nor
>> libaudit.
>>
>> loading an ubuntu livecd results in showing
>> libselinux.
>>
>> my guess since this is a development version they haven't
>> enabled SELinux support yet with gdm.
>>
>> ohh well, I guess Ill leave it at that.
>>      
>
> The gdm selinux support was obsoleted by the gdm rewrite, so it isn't
> necessary to link it with libselinux anymore.  It all gets handled by
> pam_selinux in /etc/pam.d/gdm.  In Fedora, /etc/pam.d/gdm looks like
> this:
> #%PAM-1.0
> auth     [success=done ignore=ignore default=bad] pam_selinux_permit.so
> auth       required    pam_succeed_if.so user != root quiet
> auth       required    pam_env.so
> auth       substack    system-auth
> auth       optional    pam_gnome_keyring.so
> account    required    pam_nologin.so
> account    include     system-auth
> password   include     system-auth
> session    required    pam_selinux.so close
> session    required    pam_loginuid.so
> session    optional    pam_console.so
> session    required    pam_selinux.so open
> session    optional    pam_keyinit.so force revoke
> session    required    pam_namespace.so
> session    optional    pam_gnome_keyring.so auto_start
> session    include     system-auth
>
> BTW, I would recommend testing the policy package provided by OpenSUSE
> to see if it works before trying upstream refpolicy.
>
> And report issues with their SELinux integration to their bugzilla, not
> to us.  It won't get fixed if you just post it here.
>
> Are you following the guidance at:
> http://en.opensuse.org/SELinux
>
> You have to add an additional repository to pick up their policy and associated packages.
>
> The SELinux integration work seems to be getting tracked on this blog:
> http://thetoms-random-thoughts.blogspot.com/search/label/Security
>
>    
So your telling me you can compile this
package without the audit/selinux switches,
and still run a policy?

doing a ldd /usr/sbin/gdm
shows nothing with libpam(ubuntu does).

As of now everything is opensused out
did have userspace put in, but was easily
written over by suse. Ill try
your gdm config for pam.d but Im just not
connecting the dots on this. FWIW heres what
ldd /usr/sbin/gdm  has for the libs.

linux-vdso.so.1
libXau.so.6
libdbus-glib-1.so.2
libgobject-2.0.so.0
libglib-2.0.so.0
libdbus-1.so.3
libpthread.so.0
libXdmcp.so.6
libwrap.so.0
libc.so.6
libpcre.so.0
librt.so.1
ld-linux-x86-64.so.2

I suppose I have to reinstall to get things in order.

Justin P. Mattock

  reply	other threads:[~2009-09-09 14:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 23:04 opensuse and SELinux = some dbus roblem with xdm/gdm Justin Mattock
2009-09-08 23:04 ` [refpolicy] " Justin Mattock
2009-09-09  5:33 ` Justin P. Mattock
2009-09-09  5:33   ` [refpolicy] " Justin P. Mattock
2009-09-09 12:55   ` Stephen Smalley
2009-09-09 12:55     ` [refpolicy] " Stephen Smalley
2009-09-09 14:51     ` Justin P. Mattock [this message]
2009-09-09 14:51       ` Justin P. Mattock
2009-09-09 15:03       ` Stephen Smalley
2009-09-09 15:03         ` [refpolicy] " Stephen Smalley
2009-09-09 15:38         ` Justin P. Mattock
2009-09-09 15:38           ` [refpolicy] " Justin P. Mattock
2009-09-10  9:24           ` Justin Mattock
2009-09-10  9:24             ` [refpolicy] " Justin Mattock

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=4AA7C0D5.3090706@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=refpolicy@oss1.tresys.com \
    --cc=sds@tycho.nsa.gov \
    --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.