Description of problem:
adding session required pam_namespace.so require_selinux prevents login from happening when using the MLS selinux policy
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. add session required pam_namespace.so require_selinux to /etc/pam.d/sshd
2. try to log in to the system over ssh
Nov 1 13:53:31 rhel6-wsweb sshd: pam_namespace(sshd:session): selinux_required option given and selinux is disabled
josh do you see any avc messages related to sshd_t?
And you do have allow_polyinstantiation boolean turned on?
setsebool -P allow_polyinstantiation 1
polyinstantiation is enabled and there are no AVC messages related to sshd_t or anything
(In reply to comment #3)
> polyinstantiation is enabled and there are no AVC messages related to sshd_t or
running with semodule -DB does not provide any other denials other than noatsecure siginh rlimitinh
Josh, are you really running the genuine RHEL-6 rpms?
Also, do you see the same problem when running with targeted policy?
(In reply to comment #5)
> Josh, are you really running the genuine RHEL-6 rpms?
> Also, do you see the same problem when running with targeted policy?
Yep, genuine RHEL-6 rpms from 6.1
Just tried it with targeted and I AM seeing the same problem
PS: the option is require_selinux but the logged error message is selinux_required
Ah, I forgot about this bug. This is actually a real pam_namespace bug that is fixed already in the current upstream releases (and Fedora).
(In reply to comment #7)
> Ah, I forgot about this bug. This is actually a real pam_namespace bug that is
> fixed already in the current upstream releases (and Fedora).
Any way it can find its way in to RHEL6.2?
I cannot give you any definitive information in regards to RHEL6.2 but I can say it is highly improbable that it would be fixed there.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
Is this limited to MLS? I am unable to connect even in targeted policy.
No, this is not limited to MLS. It is sufficient to test it with targeted policy.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.