STIG ID RHEL-08-020035 CAUSES GNOME TO CRASH

[lsimmons1957]

Description of problem:

After applying rhel8-playbook-stig_gui.yml, GNOME crashes after 30-40 minutes of inactivity.

SCAP Security Guide Version:

0.1.69

Operating System Version:

RHEL 8.8

Steps to Reproduce:

1. Install RHEL 8.8 "Server with GUI" configuration.
2. Install SSG 0.1.69
3. Install Ansible Core.
4. Apply rhel8-playbook-stig_gui.yml.
5. Reboot and log into GNOME.
6. Leave computer idle for 30-40 minutes.
7. Observe that GNOME is no longer accessible.
8. Observe that ALT-F2 presents a function console.

Actual Results:

GNOME session crashes.

Expected Results:

GNOME session is logged out gracefully.

Additional Information/Debugging Steps:

Don't apply RHEL-08-020035 to /etc/systemd/logind.conf.
Don't set StopIdleSessionSec=900.
Leave StopIdleSessionSec commnted out.
GNOME no longer crashes after 30-40 minutes of inactivity.

[Mab879]

Thanks for opening this issue I was able to reproduce this behavior.

We looking into solutions as the playbook implementation is technically correct for how RHEL-08-020035 is written, but this causing some fairly large usability concerns.

[lsimmons1957]

Thank you for being so responsive, Matthew. I suspect it may be a bug in RHEL itself. Sincerely, LANCE SIMMONS | Staff Cyber Information Assurance Analyst Northrop Grumman | Office of the CIO / Classified Cybersecurity (CCS) O: 310-813-3981 | P: 310-319-0564 | ***@***.******@***.***> Know your Systems, Know your People, Know your Documentation. From: Matthew Burket ***@***.***> Sent: Friday, August 11, 2023 12:26 PM To: ComplianceAsCode/content ***@***.***> Cc: Simmons, Lance [US] (ES) ***@***.***>; Author ***@***.***> Subject: EXT :Re: [ComplianceAsCode/content] STIG ID RHEL-08-020035 CAUSES GNOME TO CRASH (Issue #10986) Thanks for opening this issue I was able to reproduce this behavior. We looking into solutions as the playbook implementation is technically correct for how RHEL-08-020035<https://stigaview.com/products/rhel8/v1r11/RHEL-08-020035/> is written, but this causing some fairly large usability concerns. — Reply to this email directly, view it on GitHub<#10986 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A4VYE7QPLVBXKFFZV4QYYW3XU2BMPANCNFSM6AAAAAA3NCGGLY>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>