RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1429302 - Unable to get a shell on ssh after upgrading to 6.8 - syslogin_perform_logout: logout() returned an error
Summary: Unable to get a shell on ssh after upgrading to 6.8 - syslogin_perform_logout...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: openssh
Version: 6.8
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jakub Jelen
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-06 03:31 UTC by Venkata Tadimarri
Modified: 2021-03-11 15:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-07 09:19:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 3 Jakub Jelen 2017-03-06 08:47:31 UTC 
Hello. The problem is obviously in the option

    UseLogin yes

As far as I know, it is not supported in current RHEL7+. About the support in RHEL6 I am also in doubts, because this very fail-prone configuration with potential secureity issues.

You can also notice the AVCs below:

type=AVC msg=audit(1487690508.890:393912): avc:  denied  { execute } for  pid=3550 comm="sshd" name="login" dev=dm-0 ino=3932171 scontext=unconfined_u:system_r:sshd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:login_exec_t:s0 tclass=file
type=AVC msg=audit(1487690508.890:393912): avc:  denied  { read open } for  pid=3550 comm="sshd" name="login" dev=dm-0 ino=3932171 scontext=unconfined_u:system_r:sshd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:login_exec_t:s0 tclass=file

Most probably, the SELinux policy got stricter between the updates. I would recommend you not to use "UseLogin yes". If the customer can not avoid it, you would need to adjust the selinux-policy on that system (certainly nothing we would like to allow by default in RHEL).

Let me know if there is something more in this case or I can close it, because I don't think it is a bug.
Comment 4 Venkata Tadimarri 2017-03-06 23:21:31 UTC 
Hello Jakub,

Thanks a lot for the immediate response. I guess you can proceed with closing the bug as your update has resolved the issue for the customer.

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