From: Thomas Bleher <bleher@informatik.uni-muenchen.de>
To: 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:11:57 +0200 [thread overview]
Message-ID: <20040520121157.GA2146@jmh.mhn.de> (raw)
In-Reply-To: <20040519115039.GB4221@lkcl.net>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
* Luke Kenneth Casson Leighton <lkcl@lkcl.net> [2004-05-19 15:13]:
> On Wed, May 19, 2004 at 12:08:22PM +0200, Thomas Bleher wrote:
> > * Luke Kenneth Casson Leighton <lkcl@lkcl.net> [2004-05-19 11:06]:
> > > is this pretty much all that's required??? compared to the 2.4 stuff
> > > it's like tiny.
> > >
> > > this is all that the patch to wdm does. i'm just a little surprised
> > > (pleasantly so).
> > >
> > > --- client.c.old 2004-05-19 07:40:58.000000000 +0000
> > > +++ kdm/backend/client.c 2004-05-19 07:18:01.000000000 +0000
> > <snip patch>
> >
> > I don't think that even this is required. It should work without
> > patching, just using pam_selinux.so.
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.
> oh?
>
> do you have some example usage that i can try out, and does
> anyone have any advice on how to ensure that installation
> of debian packages (pam and selinux and kde) would result
> in pam being automatically updated?
echo "session required pam_selinux.so" >> /etc/pam.d/kdm
should do it.
/etc/pam.d/kdm is a conffile AFAIK, so there should be no problems when
updating packages.
HTH,
Thomas
--
http://www.cip.ifi.lmu.de/~bleher/selinux/ - my SELinux pages
GPG-Fingerprint: BC4F BB16 30D6 F253 E3EA D09E C562 2BAE B2F4 ABE7
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-20 12:13 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 [this message]
2004-05-20 12:49 ` Stephen Smalley
2004-05-20 14:52 ` Luke Kenneth Casson Leighton
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=20040520121157.GA2146@jmh.mhn.de \
--to=bleher@informatik.uni-muenchen.de \
--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.