|Summary:||nftables saved configuration shouldn't be world-readable|
|Product:||Red Hat Enterprise Linux 7||Reporter:||Tomas Dolezal <todoleza>|
|Component:||nftables||Assignee:||Phil Sutter <psutter>|
|Status:||CLOSED ERRATA||QA Contact:||Tomas Dolezal <todoleza>|
|Severity:||high||Docs Contact:||Ioanna Gkioka <igkioka>|
|Version:||7.4||CC:||atragler, igkioka, psutter, rkhan, sukulkar, todoleza|
|Fixed In Version:||nftables-0.8-3.el7||Doc Type:||Release Note|
The `nftables` configuration files are no longer publicly readable Previously, during installation in the `RPM` file, the `nftables` configuration file mode bits were not adjusted accordingly. As a consequence, the configuration templates in the `/etc/nftables` directory and the `etc/sysconfig/nftables.conf` main configuration file were publicly readable. With this update, the file mode bits are explicitly set to correct values when installing the configuration files. As a result, the user can now install the configuration files with the correct permissions. Note that the configuration files which are not modified by the administrator, are replaced with configuration files with the correct permissions. The modified configuration files are not replaced. In that case, for `/etc/sysconfig/nftables.conf`, an rpmnew file is created which has the correct permissions. For any files in `/etc/nftables`, no rpmnew file is created, and the user must manually set the permissions.
|:||1685238 1931790 (view as bug list)||Environment:|
|Last Closed:||2018-04-10 16:09:09 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
|Bug Blocks:||1470965, 1472751|
Description Tomas Dolezal 2017-05-16 15:02:37 UTC
Comment 2 Tomas Dolezal 2017-08-08 09:40:54 UTC
granting qa_ack for 7.5; RPL
Comment 3 Phil Sutter 2017-08-16 16:27:56 UTC
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.
Comment 5 Phil Sutter 2017-10-17 13:14:52 UTC
(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.
Comment 14 errata-xmlrpc 2018-04-10 16:09:09 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, 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