Re: Getting started with SELinux and Slackware

[Lee Lowder <friedbob@sbcglobal.net>]

Russell Coker wrote:

> 
> If Slackware doesn't include PAM then it will be quite a lot of work to add 
> PAM support to all necessary applications.
> 

Last time I tried messing with SELinux on Slack, I was told that it 
would be easier to install PAM than to modify SELinux stuff to not use it.

> It would probably be easier to modify the policy to remove *_chkpwd_t and 
> grant every daemon that needs to verify a password read access to 
> shadow_t:file.

That does not seem too difficult or complicated, so I will give that a go.

> 
> Why do you want to work on Slackware?  It seems to be a regular occurrance 
> that someone starts work on Slackware SE Linux support, their work doesn't 
> get merged into the Slackware distribution, and then it gets discarded.

Slackware is the distro I use, and have used for years.  I know it and 
amcomfortable with it.  the thought of asking Pat V to merge it never 
crossed my mind, actually.  I'm doing this because it was something I 
wanted to play with and as a learning experience.

> 
> While Debian SE Linux support isn't in the greatest shape at the moment the 
> changes are getting merged into the main packages so any work you do won't 
> get wasted.
> 
> Of course you could just use Fedora and have it all work.
> 
Would the "it just works" thing apply to CentOS as well?  Or does RHEL 
not have the same level of SELinux support as Fedora?

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