<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>mainesysadmin.com &#187; grub</title>
	<atom:link href="http://mainesysadmin.com/tag/grub/feed/" rel="self" type="application/rss+xml" />
	<link>http://mainesysadmin.com</link>
	<description>SysAdmin in Maine</description>
	<lastBuildDate>Wed, 06 Jan 2010 16:24:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>HowTo &#8211; Secure GRUB bootloader for VMware ESX and Linux</title>
		<link>http://mainesysadmin.com/2009/01/22/howto-secure-grub-bootloader-for-vmware-esx-and-linux-in-general/</link>
		<comments>http://mainesysadmin.com/2009/01/22/howto-secure-grub-bootloader-for-vmware-esx-and-linux-in-general/#comments</comments>
		<pubDate>Thu, 22 Jan 2009 20:22:01 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[grub]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[vmware]]></category>

		<guid isPermaLink="false">http://mainesysadmin.com/?p=172</guid>
		<description><![CDATA[Here are a couple of really good reasons on why you need to secure your server&#8217;s boot loader regardless if you&#8217;re using GRUB or LiLo.  In this article I am only going to cover how to configure GRUB.

Preventing Access to Single User Mode — If attackers can boot the system into single user mode, [...]]]></description>
			<content:encoded><![CDATA[<p>Here are a couple of really good reasons on why you need to secure your server&#8217;s boot loader regardless if you&#8217;re using GRUB or LiLo.  In this article I am only going to cover how to configure GRUB.</p>
<ul>
<li><em>Preventing Access to Single User Mod</em>e — If attackers can boot the system into single user mode, they are logged in automatically as root without being prompted for the root password.</li>
<li><em>Preventing Access to the GRUB Console</em> — If the machine uses GRUB as its boot loader, an attacker can use the use the GRUB editor interface to change its configuration or to gather information using the cat command.</li>
</ul>
<div>Now lets go ahead and secure your server/workstation:</div>
<ul>
<li>ssh to your server host with root access</li>
<li>type: <em>grub</em> to enter the grub console</li>
<li>type: <em>md5crypt</em> to create a md5 encrypted password (document your password unencrypted and encrypted versions)</li>
<li>open your favorite editor or download the files via your favorite ftp app.  We need:  <em>menu.lst</em> and <em>grub.conf</em> they&#8217;re located here:  <em>/boot/grub</em></li>
<li>Add the below line to the top of menu.lst and grub.conf:<br />
<em> password &#8211;md5 &#8220;your_encrypted_password&#8221; </em></li>
<li>Now add &#8220;<em>lock</em>&#8221; below each titled o/s choice that you want to prevent from booting without a password.</li>
</ul>
<p>The method I described above will prevent modification of grub boot options AND only allow you to boot those items that were not password protected with the &#8220;lock&#8221; command.</p>
<p>I went ahead and manuallly modified menu.lst and grub.conf.</p>
<p>Here is an example of a sample file that you can use as a guide.  Replace &#8220;your_encrypted_password&#8221; with the md5 hash that you generated earlier with the md5crypt command.</p>
<p><a href="http://mainesysadmin.com/docs/sample.lst">grub.conf</a></p>
<p>I found the following sites useful while writing this article:</p>
<p><a href="http://ubuntuguide.org/wiki/Ubuntu:Edgy/Security" onclick="javascript:pageTracker._trackPageview ('/outbound/ubuntuguide.org');">http://ubuntuguide.org/wiki/Ubuntu:Edgy/Security</a></p>
<p><a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/security-guide/s1-wstation-boot-sec.html#S2-WSTATION-BOOTLOADER" onclick="javascript:pageTracker._trackPageview ('/outbound/www.redhat.com');">http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/security-guide/s1-wstation-boot-sec.html#S2-WSTATION-BOOTLOADER</a></p>
<p><a href="http://www.linux.com/feature/53569" onclick="javascript:pageTracker._trackPageview ('/outbound/www.linux.com');">http://www.linux.com/feature/53569</a></p>
]]></content:encoded>
			<wfw:commentRss>http://mainesysadmin.com/2009/01/22/howto-secure-grub-bootloader-for-vmware-esx-and-linux-in-general/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
