|
|||||||||||
|
Bug#442443: marked as done (grub-installer: Please do not store the GRUB password in cleartext)
From: Debian Bug Tracking System <owner(at)bugs.debian.org>
Date: Sat Oct 27 2007 - 10:09:02 EDT
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) attached mail follows:
Package: grub-installer
(originally sent by Alex to the -boot list. As I find this an interesting suggestion, I turn this into a wishlist bug against grub-installer) Observed with today's debian-testing-amd64-businesscard.iso. (Testing with a sid installer) The debian installer allows the user to enter a password for GRUB to access advanced features. If the user does so, the password is included in cleartext in /boot/grub/menu.lst GRUB has the capability to use an md5 hash of a password instead of storing the password. These are generated with the grub command md5crypt. For example, to generate a md5 hash of the password "foobar" (no quotes): echo -e "md5crypt\nfoobar" | sudo grub --batch | grep "Encrypted" | sed -e 's/Encrypted: //g' There may be a cleaner way to do this but the above will work. Then, in /boot/grub/menu.lst, where you would write: password foobar instead write (the output from the above command) password --md5 $1$SZmo8$vxbhcjqNC4kHpqZi5n3r81 It is important not to store the password in cleartext for several reasons. Some users (such as myself) may use a password either similar to or identical to the root or user password on the machine for the bootloader. I boot to an encrypted root, but of course /boot is on an unencrypted volume so the password could be snooped. I understand the rationale that on a normal system, if you have read access to menu.conf then you have write access (eg, by rooting the system) and could just clear the password anyway, but given that GRUB provides such a simple way to use a hash instead I think Debian should implement this. As always, thanks for the wonderful, free operating system. Many of us appreciate your effort (including our entire cluster:-), and my two personal machines)
Alex Roper
-- attached mail follows:
Source: grub-installer
Source-Version: 1.27
We believe that the bug you reported is fixed in the latest version of
grub-installer, which is due to be installed in the Debian FTP archive:
grub-installer_1.27.dsc
to pool/main/g/grub-installer/grub-installer_1.27.dsc
grub-installer_1.27.tar.gz
to pool/main/g/grub-installer/grub-installer_1.27.tar.gz
grub-installer_1.27_i386.udeb
to pool/main/g/grub-installer/grub-installer_1.27_i386.udeb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 442443@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Otavio Salvador <otavio@debian.org> (supplier of updated grub-installer package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 27 Oct 2007 11:58:04 -0200
Source: grub-installer
Binary: grub-installer
Architecture: source i386
Version: 1.27
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Otavio Salvador <otavio@debian.org>
Description:
grub-installer - Install GRUB on a hard disk (udeb)
Closes: 442443
Changes:
grub-installer (1.27) unstable; urgency=low
.
[ Romain Perier ]
This archive was generated by hypermail 2.1.8 : Wed Mar 19 2008 - 03:12:10 EDT |
||||||||||
|
|||||||||||