<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Recovering root passwords with Fedora Core</title>
	<atom:link href="http://prefetch.net/blog/index.php/2005/10/22/recovering-root-passwords-with-fedora-core/feed/" rel="self" type="application/rss+xml" />
	<link>http://prefetch.net/blog/index.php/2005/10/22/recovering-root-passwords-with-fedora-core/</link>
	<description>Blog O' Matty</description>
	<lastBuildDate>Tue, 07 Feb 2012 02:31:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Rob</title>
		<link>http://prefetch.net/blog/index.php/2005/10/22/recovering-root-passwords-with-fedora-core/comment-page-1/#comment-28</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Thu, 27 Oct 2005 02:08:18 +0000</pubDate>
		<guid isPermaLink="false">http://daemons.net/~matty/blog/?p=229#comment-28</guid>
		<description>This only works if you skimped on security and the root password is not required to enter single-user mode. Of course, you can always boot a repair disk, mount the root filesystem and edit the password out of /mnt/etc/passwdfor root. This is why, on a production system where you can&#039;t guarantee, 100%, physical security of your servers, you should have
(a) A firmware password to prevent changing hardware parameters
(b) Disable booting from devices other than the fixed disk, in firmware
(c) Root password required to acess the shell in single-user-mode.
(d) Bootstrap loader prtection to prevent changing boot parameters from the command line.
etc.</description>
		<content:encoded><![CDATA[<p>This only works if you skimped on security and the root password is not required to enter single-user mode. Of course, you can always boot a repair disk, mount the root filesystem and edit the password out of /mnt/etc/passwdfor root. This is why, on a production system where you can&#8217;t guarantee, 100%, physical security of your servers, you should have<br />
(a) A firmware password to prevent changing hardware parameters<br />
(b) Disable booting from devices other than the fixed disk, in firmware<br />
(c) Root password required to acess the shell in single-user-mode.<br />
(d) Bootstrap loader prtection to prevent changing boot parameters from the command line.<br />
etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

