With UEFI coming to a computer near you in the future... and with the potential that Red
Hat would leave /etc/grub.conf being a standard link pointing to the current target that
is functional... Use "/etc/grub.conf" in checks and automation. Be explicit in
the prose promoting why. Acknowledge awareness that it is a symlink, and whatever target
it points to is the current functional one.
Nix that implementation though if (when?) different grub.conf files have different content
that affects functionality, based on where they are and how used.
R,
-Joe
________________________________
From: David Smith <dsmith(a)eclipse.ncsc.mil>
To: scap-security-guide(a)lists.fedorahosted.org
Sent: Thursday, October 25, 2012 2:43 PM
Subject: grub.conf thoughts
There are several rules which tell the reader to modify or look at grub.conf. A few of
them specify looking at /boot/grub/grub.conf, since /etc/grub.conf is a symlink. The
symlink points to an alternate location on some systems (my current workstation included):
/boot/efi/EFI/redhat/grub.conf.
Thoughts on either including that in the rule text, or just simply referring the reader to
/etc/grub.conf?
_______________________________________________
scap-security-guide mailing list
scap-security-guide(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide