GNOME Bugzilla – Bug 661635
gconfd saved_state file has executable tag set
Last modified: 2018-08-17 13:56:08 UTC
Created attachment 198916 [details] [review] sets the mode to 0600 (read + write) instead of 0700 gconfd seems to be setting the executable bit on a file which presumably has no need to be executable paulm@noobuntu:~/.gconfd$ ls -l total 1624 -rwx------ 1 paulm paulm 1654806 2011-05-05 13:54 saved_state This could (perhaps in combination with other factors) be a security issue and also cause warnings from security tools that look for files with potentially dangerous or unexpected attributes. (copied from https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/777565) HEAD is still affected: http://git.gnome.org/browse/gconf/tree/gconf/gconfd.c#n1739 The attached patch is copied from Launchpad without refreshing against HEAD.
GConf has been deprecated since 2011. GConf is not under active development anymore. Its codebase has been archived: https://gitlab.gnome.org/Archive/gconf/commits/master dconf and gsettings are its successors. See https://developer.gnome.org/gio/stable/ch34.html and https://developer.gnome.org/GSettings/ for porting info. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of dconf/gsettings. Thanks!