This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 227770 - [LSPP] unable to login with 'secadm_r' role
[LSPP] unable to login with 'secadm_r' role
Status: CLOSED DUPLICATE of bug 227733
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: openssh (Show other bugs)
5.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-07 19:00 EST by Klaus Heinrich Kiwi
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-02-08 15:38:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Klaus Heinrich Kiwi 2007-02-07 19:00:57 EST
Description of problem:
Can't login using 'secadm_r' role, no matter the user (given that the user has
access to this role)

Version-Release number of selected component (if applicable):
selinux-policy-mls-2.4.6-32.el5
selinux-policy-2.4.6-32.el5

How reproducible:
always

Steps to Reproduce:
1. In a lspp-configured system, try loggin in with 'ssh <user>/secadm_r@<host>'
2. enter <user>'s password

  
Actual results:
failed to log-in

Expected results:
log-in successful

Additional info:
This seems similar to Bug #227733 - opening for tracking purposes. Please mark
as duplicate if desired.
Comment 1 Klaus Heinrich Kiwi 2007-02-08 20:16:09 EST
Tomas, any special reason for closing as NOTABUG? Does this means this won't be
fixed?

 Thanks,

Klaus
Comment 2 Tomas Mraz 2007-02-09 09:21:41 EST

*** This bug has been marked as a duplicate of 227733 ***
Comment 3 Kylene J Hall 2007-02-09 12:11:22 EST
My partitions are rather hosed at the moment so I can't double check this with
any certainty but that is what I saw.  I cleared /var/log/secure and restarted
the syslog service before attempting the ssh to make sure I got just the related
stuff.

Here is /etc/pam.d/sshd
auth       include      system-auth
auth       required     pam_tally2.so deny=5 onerr=fail

account    required     pam_nologin.so
account    include      system-auth
account    required     pam_tally2.so

password   include      system-auth

session    required     pam_selinux.so close
session    include      system-auth
session    required     pam_loginuid.so require_auditd
session    required     pam_namespace.so debug # FIXME, remove debug

Note You need to log in before you can comment on or make changes to this bug.