Bug 2228461

Summary: system account with uid >= 1000 is badly detected as user interactive account [rhel-8.6.0.z]
Product: Red Hat Enterprise Linux 8 Reporter: RHEL Program Management Team <pgm-rhel-tools>
Component: scap-security-guideAssignee: Marcus Burghardt <maburgha>
Status: CLOSED ERRATA QA Contact: Milan Lysonek <mlysonek>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.7CC: ggasparb, jcerny, maburgha, mhaicman, mlysonek, peter.vreman, rmetrich, vpolasek, wsato
Target Milestone: rcKeywords: Triaged, ZStream
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: scap-security-guide-0.1.69-2.el8_6 Doc Type: Enhancement
Doc Text:
Feature: Extend the criteria used for selecting interactive users in order to avoid special users without shell to be considered interactive users. Reason: Rules related to interactive users where considering any user with uid >= 1000 as interactive users. However, there are valid cases where users with uid >= 1000 have no interactive shell and therefore should not be considered interactive users. Result: All rules related to interactive users are aligned using the same criteria to identify interactive users in a system. These criteria are: - uid >= 1000 - except nobody and nfsnobody users - except users with /sbin/nologin shell
Story Points: ---
Clone Of: 2178740 Environment:
Last Closed: 2023-08-29 09:11:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2178740    
Bug Blocks:    

Comment 15 errata-xmlrpc 2023-08-29 09:11:57 UTC
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 (scap-security-guide bug fix 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-2023:4793