From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Thomas Bleher <bleher@informatik.uni-muenchen.de>,
SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: is this pretty much it (to patch kdm 3.2.2)?
Date: Thu, 20 May 2004 14:52:58 +0000 [thread overview]
Message-ID: <20040520145258.GF8810@lkcl.net> (raw)
In-Reply-To: <1085057380.521.70.camel@moss-spartans.epoch.ncsc.mil>
On Thu, May 20, 2004 at 08:49:40AM -0400, Stephen Smalley wrote:
> On Thu, 2004-05-20 at 08:11, Thomas Bleher wrote:
> > I just rechecked, and it is indeed working fine on a SuSE box
> > (kdebase3-kdm-3.2.2-8) without any patches, just using the selinux pam
> > module.
>
> Interesting. We weren't able to use pam_selinux with gdm, as
> pam_open_session was called from a different process.
i _do_ notice in permissive / audit mode that kdeinit attempts to
do an su:
May 20 14:53:58 tv kernel: audit(1085064838.508:0): avc: denied {
execute } for pid=2616 exe=/usr/bin/kdeinit name=su dev=hda5 ino=93620
scontext=lkcl:user_r:user_t tcontext=system_u:object_r:su_exec_t
tclass=file
May 20 14:53:58 tv kernel: audit(1085064838.509:0): avc: denied {
getattr } for pid=2616 exe=/usr/bin/kdeinit path=/bin/su dev=hda5
ino=93620 scontext=lkcl:user_r:user_t
tcontext=system_u:object_r:su_exec_t tclass=file
this is _without_ doing a pam session, but with a patched
kdm.
checking the source code... kdm/process/client.c:StartClient()
the get_default_context is at line 1102.
pam_open_session() is at line 1172.
track track track... oo, wossat? a fork()??? ah, that's at line 1184.
okay, so i prepare a context, then open the pam session, and _then_
there's a fork (this is horrible code, btw - really large switch
statements and yuk indentation: i'm actually giving up looking for
the end of the switch statement or another case or the default :)
so, if pam_open_session() does all the work, then i don't need to
have patched kdm, and a line in /etc/pam.d/kdm to include module
pam_selinux would do the job just as well.
oh well :)
l.
--
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:[~2004-05-20 14:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 7:42 is this pretty much it (to patch kdm 3.2.2)? Luke Kenneth Casson Leighton
2004-05-19 10:08 ` Thomas Bleher
2004-05-19 11:50 ` Luke Kenneth Casson Leighton
2004-05-20 12:11 ` Thomas Bleher
2004-05-20 12:49 ` Stephen Smalley
2004-05-20 14:52 ` Luke Kenneth Casson Leighton [this message]
2004-05-20 15:39 ` Russell Coker
2004-05-20 16:14 ` Luke Kenneth Casson Leighton
2004-05-20 16:26 ` Stephen Smalley
2004-05-20 16:45 ` Luke Kenneth Casson Leighton
2004-05-20 17:06 ` Luke Kenneth Casson Leighton
2004-05-20 17:24 ` Luke Kenneth Casson Leighton
2004-05-19 12:16 ` Stephen Smalley
2004-05-19 12:34 ` Stephen Smalley
2004-05-19 12:47 ` Luke Kenneth Casson Leighton
2004-05-19 14:05 ` Russell Coker
2004-05-19 14:39 ` Luke Kenneth Casson Leighton
2004-05-19 17:23 ` kdm 3.2.2 and kernel image 2.6.6 selinux .debs available Luke Kenneth Casson Leighton
2004-05-19 17:37 ` Luke Kenneth Casson Leighton
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=20040520145258.GF8810@lkcl.net \
--to=lkcl@lkcl.net \
--cc=bleher@informatik.uni-muenchen.de \
--cc=sds@epoch.ncsc.mil \
--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.