From: Dennis Wronka <linuxweb@gmx.net>
To: SELinux Mailing List <selinux@tycho.nsa.gov>
Subject: Re: Question about newrole
Date: Tue, 5 Aug 2008 22:27:31 +0800 [thread overview]
Message-ID: <200808052227.31582.linuxweb@gmx.net> (raw)
In-Reply-To: <1217945614.2994.74.camel@moss-spartans.epoch.ncsc.mil>
[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]
Just for the record, sent the initial reply to Stephen only.
Sorry for the glitch.
Rest at the bottom.
On Tuesday 05 August 2008 22:13:34 Stephen Smalley wrote:
> On Tue, 2008-08-05 at 21:55 +0800, Dennis Wronka wrote:
> > Hi folks,
> >
> > I'd like to ask about a problem I am experiencing with newrole.
> > When I use newrole in permissive-mode I have no problems changing the
> > role. Also I don't get any audit-messages.
> > But when I switch to enforcing-mode I cannot use newrole, it keeps
> > telling me "incorrect password for root", although it clearly is correct.
> > I suspect a problem in interaction between newrole and unix_chkpwd, but
> > am not entirely sure about it.
> >
> > Problem is that I don't get any audits from SELinux, only errors in
> > auth.log from unix_chkpwd:
> > check_pass; user unknown
> > password check failer for user (root)
> >
> > I am working with the latest reference-policy, adjusted here and there to
> > fit the needs of my distro.
> >
> > Thanks for any suggestions.
>
> What version of pam are you using? What distro?
> There were changes made to pam_unix and unix_chkpwd for selinux.
> Also, how are you building newrole?
I am using PAM 1.0.1 on the current development-version of EasyLFS. I am
currently working on the integration of SELinux and seem to be hanging on
this point.
I haven't set much focus towards newrole in the previous releases, but want to
do so now.
newrole is the one from the policycoreutils 2.0.49, built simply with make &&
make install.
Btw, I think the same problem applies to run_init, will have to check to
confirm though.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-05 14:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 13:55 Question about newrole Dennis Wronka
2008-08-05 14:13 ` Stephen Smalley
2008-08-05 14:27 ` Dennis Wronka [this message]
2008-08-05 14:17 ` Xavier Toth
2008-08-05 14:32 ` Dennis Wronka
2008-08-05 14:48 ` Stephen Smalley
2008-08-05 15:04 ` Justin Mattock
2008-08-05 15:10 ` Dennis Wronka
2008-08-05 15:19 ` Justin Mattock
2008-08-05 15:05 ` Dennis Wronka
2008-08-05 15:23 ` Justin Mattock
2008-08-05 15:23 ` Dennis Wronka
2008-08-05 15:36 ` Stephen Smalley
2008-08-05 15:46 ` Dennis Wronka
2008-08-05 20:21 ` Justin Mattock
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=200808052227.31582.linuxweb@gmx.net \
--to=linuxweb@gmx.net \
--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.