Several of the GConf checks were using xmlfilecontent, which I liked, so I 
changed the ones that weren't to use it. However, the checks that had been 
using xmlfilecontent were improperly pointing to /etc/gconf/gconf.xml.defaults, 
when we wanted to be peering into gconf.xml.mandatory instead (this is where 
the gconf2-tool instructions were writing their values).

To add support to ensure these checks will no longer report a failure on 
machines that aren't using X, I added an extended definition check and the 
appropriate package checks to point to the lowest level package that installs 
GConf settings, namely the GConf2 package. On servers that don't have this 
package installed, the check will pass.

- Maura Dailey

Maura Dailey (1):
  Rewrote various GConf checks to standardize on xmlfilecontent tests
    and ensured they were actually checking the correct location
    (gconf.xml.mandatory, not gconf.xml.defaults).

 .../input/checks/gconf_gnome_disable_automount.xml |   59 +++++++++++---------
 .../checks/gconf_gnome_disable_thumbnailers.xml    |   34 ++++++-----
 ...f_gnome_screensaver_idle_activation_enabled.xml |   19 ++++--
 .../checks/gconf_gnome_screensaver_idle_delay.xml  |   24 +++++---
 .../gconf_gnome_screensaver_lock_enabled.xml       |   14 +++--
 .../checks/gconf_gnome_screensaver_mode_blank.xml  |   12 +++-
 RHEL6/input/checks/package_GConf2_installed.xml    |   26 +++++++++
 .../input/checks/templates/packages_installed.csv  |    1 +
 RHEL6/input/fixes/bash/package_GConf2_installed.sh |    1 +
 9 files changed, 124 insertions(+), 66 deletions(-)
 create mode 100644 RHEL6/input/checks/package_GConf2_installed.xml
 create mode 100644 RHEL6/input/fixes/bash/package_GConf2_installed.sh

_______________________________________________
scap-security-guide mailing list
[email protected]
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

Reply via email to