Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause:
Permissions of updated database files were not restored and were set to the default ones for new files.
Consequence:
The database files could can be unreadable with certain umask.
Fix:
Permissions of updated database files are restored in current version of dconf.
Result:
Permissions of database files do not change between their updates.
Hi,
I've filed an upstream bug with a patch which restores the permissions after the file has been updated. I've also asked about the setting of default permissions suggested by you so we know upstream's opinion on this.
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/RHBA-2017:2302
Description of problem: 'dconf update' changes permissions on 'etc/dconf/db/local' if umask is set Version-Release number of selected component (if applicable): dconf-0.16.0-6.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Login as root 2. Set umask by executing 'umask 0077' 3. Execute 'touch /etc/dconf/db/local.d/00-temp' to create a new file under ' /etc/dconf/db/local.d/' directory. 4. Execute 'dconf update' Actual results: '/etc/dconf/db/local' file is not readable by non-root users. # ls -lh /etc/dconf/db/local -rw-------. 1 root root 61 Sep 24 04:08 /etc/dconf/db/local Expected results: '/etc/dconf/db/local' should be readable by non-root users. Additional info: strace shows a new file is created and renamed to '/etc/dconf/db/local' : 28288 04:08:37 open("/etc/dconf/db/local", O_WRONLY) = 3 <0.000017> 28288 04:08:37 open("/etc/dconf/db/local.L2LU5X", O_RDWR|O_CREAT|O_EXCL, 0666) = 4 <0.000257> 28288 04:08:37 fallocate(4, 0, 0, 61) = 0 <0.000088> 28288 04:08:37 write(4, "GVariant\0\0\0\0\0\0\0\0\30\0\0\0<\0\0\0\0\0\0(\1\0\0\0"..., 61) = 61 <0.000017> 28288 04:08:37 fstatfs(4, {f_type=0x58465342, f_bsize=4096, f_blocks=7720261, f_bfree=5457808, f_bavail=5457808, f_files=30896128, f_ffree=30720557, f_fsid={64768, 0}, f_namelen=255, f_frsize=4096}) = 0 <0.000014> 28288 04:08:37 lstat("/etc/dconf/db/local", {st_dev=makedev(253, 0), st_ino=69189057, st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=61, st_atime=2015/09/24-04:06:59, st_mtime=2015/09/24-04:06:38, st_ctime=2015/09/24-04:06:39}) = 0 <0.000015> 28288 04:08:37 fsync(4) = 0 <0.061986> 28288 04:08:38 close(4) = 0 <0.000063> 28288 04:08:38 rename("/etc/dconf/db/local.L2LU5X", "/etc/dconf/db/local") = 0 <0.000061> 28288 04:08:38 write(3, "\0\0\0\0\0\0\0\0", 8) = 8 <0.000024> 28288 04:08:38 close(3)