Indeed, this bug has been caused by the missing execution marks of all
files in /etc/grub.d, as a test has proved.
Thanks for your hint!
To prevent further trouble, this should be documented in all the files
which are connected with grub2. Furthermore, all procedures which touch
/boot/grub/grub.cfg should be obliged :
- to create a security copy of this file and to announce its name and
directory to the user;
- to ask the user in case of leaving grub.cfg empty, whether he wants
to continue. If he does not, grub.cfg must be restored with the
original content before the procedure goes to exit.
I hope that the Debian developers and their security team agree to this
demand and take steps to realize it as soon as possible (This bug has
caused numerous hours of avoidable work including at least 16 e-mails!)
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
