Hide Forgot
Description of problem: like iptables, nftables configuration should not be readable by other than root user for security reasons. It should not have any functional implications. Version-Release number of selected component (if applicable): nftables-0.6-4.el7.x86_64 How reproducible: always Actual results: stat -c '%A %U:%G %n' /etc/sysconfig/*tabl* /etc/nftables{,/*} -rw------- root:root /etc/sysconfig/ebtables-config -rw------- root:root /etc/sysconfig/ip6tables-config -rw------- root:root /etc/sysconfig/iptables-config -rw-r--r-- root:root /etc/sysconfig/nftables.conf drwxr-xr-x root:root /etc/nftables -rw-r--r-- root:root /etc/nftables/bridge-filter -rw-r--r-- root:root /etc/nftables/inet-filter -rw-r--r-- root:root /etc/nftables/ipv4-filter -rw-r--r-- root:root /etc/nftables/ipv4-mangle -rw-r--r-- root:root /etc/nftables/ipv4-nat -rw-r--r-- root:root /etc/nftables/ipv6-filter -rw-r--r-- root:root /etc/nftables/ipv6-mangle -rw-r--r-- root:root /etc/nftables/ipv6-nat Expected results: ownership stays same, g,o mode is 0. the same applies for /etc/nftables/ folder Additional info:
granting qa_ack for 7.5; RPL
Regarding to release notes, clarify what happens if users have modified configs: Are they changed automatically? Can we make RPM change them? Not sure if users become aware of permission changes for created *.rpmnew files.
(In reply to Phil Sutter from comment #3) > Regarding to release notes, clarify what happens if users have modified > configs: Are they changed automatically? Can we make RPM change them? Not > sure if users become aware of permission changes for created *.rpmnew files. If unmodified, all config files are overwritten with updates from RPM and hence permissions are changed as well. If files were modified by the user, for /etc/sysconfig/nftables.conf an rpmnew file is created (with correct permissions), files in /etc/nftables are just left unmodified (and no rpmnew file is created). Not sure why the latter happens, but this should be documented at least.
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, 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/RHEA-2018:0882