All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: Thomas Bleher <bleher@informatik.uni-muenchen.de>
Cc: SELinux ML <selinux@tycho.nsa.gov>, krahmer@suse.de
Subject: Re: file_contexts patch
Date: Mon, 19 Jul 2004 09:59:48 +1000	[thread overview]
Message-ID: <200407190959.48713.russell@coker.com.au> (raw)
In-Reply-To: <20040718150357.GA322@rom.cip.ifi.lmu.de>

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?

Also it shouldn't be that difficult to fix the SUSE code.

> > Are you running kcheckpass as root (maybe SETUID)?
>
> It's sgid shadow.

That's entirely the wrong approach.  Any bug in kcheckpass on a SUSE system 
will give full access to /etc/shadow.

> > If so then SUSE would be
> > using PAM without my patch to pam_unix.so which allows unix_chkpwd to be
> > called if /etc/shadow can't be opened as root (without that patch it just
> > aborts).  Also does SUSE have unix_verify (again part of my patch)
> > installed? If not then the default policy will not work in all
> > situations...
>
> Yeah, I had to give login, ssh, kdm, ... the auth attribute.
> I do not know which part of the patch is missing, it's been a while
> since I looked at the PAM code.
> At the time I made the packages I simply gave up on PAM after a while
> because it was too complicated and I didn't want to find out how suse's
> module differed from the rest of the world...
> I guess it's time I dig again into this mess, sigh.
> I really wish there was someone actively maintaining this code.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page

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

  reply	other threads:[~2004-07-18 23:59 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 [this message]
2004-07-24 19:08               ` Thomas Bleher
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=200407190959.48713.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=bleher@informatik.uni-muenchen.de \
    --cc=krahmer@suse.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.