You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If I understand correctly, the template file etc/sysconfig/rhel_sysconfig_init.j2 won't work on RHEL7 and newer, since it uses "systemd" instead of "init".
I assume the "Daemon umask" (NSA 2.2.4.1) set in the template file won't have any effect and needs to be replaced by something else.
I also suspect RHEL6 was the last release where setting os_security_init_single: trueactually worked. This variable is referenced in the template. RHEL7 enforces a single user mode password by default, so os_security_init_single might not be needed any longer.
Role Version
7.14.2
The text was updated successfully, but these errors were encountered:
If I understand correctly, the template file etc/sysconfig/rhel_sysconfig_init.j2 won't work on RHEL7 and newer, since it uses "systemd" instead of "init".
You're right, I tested it. This only works for applications that are getting started with init-scripts, not with systemd.
We should probably use pam and /etc/profile for this.
Describe the bug
If I understand correctly, the template file
etc/sysconfig/rhel_sysconfig_init.j2
won't work on RHEL7 and newer, since it uses "systemd" instead of "init".I assume the "Daemon umask" (NSA 2.2.4.1) set in the template file won't have any effect and needs to be replaced by something else.
I also suspect RHEL6 was the last release where setting
os_security_init_single: true
actually worked. This variable is referenced in the template. RHEL7 enforces a single user mode password by default, soos_security_init_single
might not be needed any longer.Role Version
The text was updated successfully, but these errors were encountered: