Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
This bug was initially created as a copy of Bug #2100464
I am copying this bug because:
We need the same update of the RHEL 8(.6). The functionality of has been lost there too, which negatively affects how secured the system can be.
Description of problem:
The Common Criteria OSPP SFR
https://www.niap-ccevs.org/MMO/PP/-442-/#FMT_SMF_EXT.1.1
has as one of the security functions that the product should support session timeout. Other security policies have similar requirements.
In the past, a de facto solution was to use sshd's ClientAliveInterval and ClientAliveCountMax options. However, those options were never intended for this purpose, and on RHEL 9 with openssh rebase their behaviour has changed to the extend that it cannot be reliably used for sessions timeouts.
At the same time, systemd-logind has a notion of sessions (and not just for remote connections), and it already has some logic for handling idle sessions. Unfortunately, the IdleAction and IdleActionSec options from /etc/systemd/logind.conf deal with the whole system's status, it does not have the per-session granularity or ability to terminate idle session.
We'd like the systemd-logind's functionality to be extended with logind.conf's option SessionIdleTerminateSec (or similar name) which would set per-session idle accounting and termination of sessions idle for more then the set limit.
Version-Release number of selected component (if applicable):
systemd-250-6.el9_0.x86_64
How reproducible:
Deterministic.
Steps to Reproduce:
1. Try to setup session timeout on RHEL where idle sessions would be terminated but the system as whole would keep running.
Actual results:
It is currently not possible.
Expected results:
It should be possible for example by adding
SessionIdleTerminateSec=10min
to /etc/systemd/logind.conf
Additional info:
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 (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:7727