From: Thomas Bleher <bleher@informatik.uni-muenchen.de>
To: SELinux ML <selinux@tycho.nsa.gov>
Cc: russell@coker.com.au, krahmer@suse.com
Subject: Re: file_contexts patch
Date: Sat, 24 Jul 2004 21:08:11 +0200 [thread overview]
Message-ID: <20040724190811.GC2016@jmh.mhn.de> (raw)
In-Reply-To: <200407190959.48713.russell@coker.com.au>
[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]
* Russell Coker <russell@coker.com.au> [2004-07-19 03:25]:
> On Mon, 19 Jul 2004 01:03, Thomas Bleher <bleher@informatik.uni-muenchen.de>
> wrote:
> > > unix_chkpwd has been around for years, I can't believe that it's
> > > something that they haven't got to it yet.
> >
> > unix_chkpwd is included in the PAM package, it's just that suse has
> > developed their own pam module (pam_unix2.so) which doesn't use
> > unix_chkpwd AFAIK.
>
> Why can't you just use pam_unix.so instead?
At the time I installed SELinux on the computers here my primary focus
was to get a working system without breaking too much so I didn't want
to muck around with pam config if possible.
After this mail exchange I looked at the code again. And indeed, the
patch Russell mentioned earlier (to make pam_unix use unix_chkpwd if it
can't access /etc/shadow) was missing. After adding this patch, pam now
runs fine without every login program needing the auth attribute.
So, for everyone who uses my packages, please update to the latest pam,
which you can get from my site. After that, replace every occurrence of
pam_unix.so or pam_unix2.so under /etc/pam.d with pam_unix_auth.so,
pam_unix_acct.so, pam_unix_passwd.so or pam_unix_session.so,
respectively.
Thomas
PS: Thanks to Russell for nudging me to this.
--
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-07-24 19:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 20:15 file_contexts patch Thomas Bleher
2004-07-16 22:02 ` Russell Coker
2004-07-16 22:42 ` Thomas Bleher
2004-07-17 1:59 ` Russell Coker
2004-07-17 19:53 ` Thomas Bleher
2004-07-18 2:58 ` Russell Coker
2004-07-18 15:03 ` Thomas Bleher
2004-07-18 23:59 ` Russell Coker
2004-07-24 19:08 ` Thomas Bleher [this message]
2004-07-26 20:25 ` Stephen Smalley
2004-07-26 22:06 ` Thomas Bleher
2004-07-28 6:48 ` Russell Coker
2004-07-28 19:25 ` Stephen Smalley
2004-07-27 0:36 ` Valdis.Kletnieks
2004-07-27 13:38 ` Stephen Smalley
2004-07-27 17:17 ` Valdis.Kletnieks
2004-07-28 2:53 ` Russell Coker
2004-07-30 13:33 ` Stephen Smalley
2004-07-17 10:15 ` Luke Kenneth Casson Leighton
2004-07-17 13:52 ` Thomas Bleher
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=20040724190811.GC2016@jmh.mhn.de \
--to=bleher@informatik.uni-muenchen.de \
--cc=krahmer@suse.com \
--cc=russell@coker.com.au \
--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.