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.

Description of problem: Upon installation using DISA security profile , it creates two different files instead of creating link in  /etc/pam.d/.


Version-Release number of selected component (if applicable): RHEL 7.3


How reproducible: Ever


Steps to Reproduce:

1. Start with normal install. 

2.Setup network and hostname

3.Configure Time and Date

4.Select security policy, choose DISA draft stig server with gui's
Software selection, choose server with gui, select Java Platform, KDE, Network Client, Compatibility Libraries, and Security Tools

5.Configure installation destination, configure per DISA requirements, with ext4. Then create mount points. 

6.Accept changes and begin installation add root password and create generic admin account .

7.Let system finish installing.  


Actual results: It creates 2 different files 
[hemant@dhcp4-96 pam.d]$ ls -l
-rw-r--r--. 1 root root 1252 Feb  2 20:19 system-auth
-rw-r--r--. 1 root root 1015 Feb  2 20:17 system-auth-ac



Expected results:
[root@dhcp4-96 pam.d]#
lrwxrwxrwx. 1 root root   14 Feb  7 00:21 system-auth -> system-auth-ac


Additional info:
Need to Debug the DISA security draft.

I am sorry but pam package is not the appropriate component to report bugs against for the DISA security policy settings/installer. This needs to be fixed in the DISA installer - I have no idea which component that is.

Also just FYI - when there are both system-auth and system-auth-ac as regular files then the system-auth is used. The system-auth-ac contents is irrelevant.

This looks like oscap-anaconda-addon. Let's see if they have any input on this issue.

Hello,
most likely culprit in this case is scap-security-guide, which provides remediation scripts utilized to harden the system.

I have just tried described scenario for RHEL 7.4 installation and links are preserved. So if you don't mind, I will assume it's fixed, thus closing this issue.

If you need it for RHEL 7.3 installation, you can still use datastream from network - use one from scap-security-guide-0.1.33-5.el7

Feel free to reopen if your mileage varies.