Description of problem:
Update ansible playbooks to filter out regular expression elements from login banners the same as bash remediation do:
|
expanded=$(echo "$login_banner_text" | sed 's/(\\\\\x27)\*/\\\x27/g;s/(\\\x27)\*//g;s/(\\\\\x27)/tamere/g;s/\^(\(.*\)|.*$/\1/g;s/\[\\s\\n\][+*]/ /g;s/\\//g;s/(n)\*/\\n/g;s/\x27/\\\x27/g;') |
Here is the ansible playbook:
|
value: string '{{ login_banner_text }}' |
Addition Information:
This is something intentionally targeted to be fixed in #3679 but priorities have been changed so this is issue is being created to not block the PR.
#3679 fixed several issues with bash remediation for dconf_gnome_login_banner_text but test scenarios to cover all possible variable values are missing and the OVAL check still doesn't know how to handle when key=value is under some wrong section leading to a false positive, for example:
[org/gnome/wrong-section]
banner-message-text='Valid value'
Description of problem:
Update ansible playbooks to filter out regular expression elements from login banners the same as bash remediation do:
content/linux_os/guide/system/accounts/accounts-banners/gui_login_banner/dconf_gnome_login_banner_text/bash/shared.sh
Line 7 in 987a0f6
Here is the ansible playbook:
content/linux_os/guide/system/accounts/accounts-banners/gui_login_banner/dconf_gnome_login_banner_text/ansible/shared.yml
Line 35 in 987a0f6
Addition Information:
This is something intentionally targeted to be fixed in #3679 but priorities have been changed so this is issue is being created to not block the PR.
#3679 fixed several issues with bash remediation for dconf_gnome_login_banner_text but test scenarios to cover all possible variable values are missing and the OVAL check still doesn't know how to handle when
key=valueis under some wrong section leading to a false positive, for example: