<?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: Named&#8217;s working directory not writeable</title>
	<atom:link href="http://famousphil.com/blog/2010/04/nameds-working-directory-not-writeable/feed/" rel="self" type="application/rss+xml" />
	<link>http://famousphil.com/blog/2010/04/nameds-working-directory-not-writeable/</link>
	<description>My Personal Blog</description>
	<lastBuildDate>Wed, 02 May 2012 12:08:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Famous Phil</title>
		<link>http://famousphil.com/blog/2010/04/nameds-working-directory-not-writeable/comment-page-1/#comment-1332</link>
		<dc:creator>Famous Phil</dc:creator>
		<pubDate>Thu, 19 Aug 2010 16:53:53 +0000</pubDate>
		<guid isPermaLink="false">http://famousphil.com/?p=449#comment-1332</guid>
		<description>That is a good point that I probably should have covered.  It does make my system less secure, but it does get rid of the errors that I have to read through in the logs.  I believe I am one of the few admins that actually cares enough to read through logs entirely without parsers and it takes a lot of time to do.  It also helps me optimize everything.  

Because of the time I spend reading through errors like this, I don&#039;t really mind having a slightly more insecure system because I have full system backups, I limit user access, and I monitor for any modifications to files that are not within the /home directory.  So even if an exploit was discovered before I knew about it (it has happened once in the past 5 years), I&#039;d still have everything repaired within 30 minutes of the initial exploit into my system.</description>
		<content:encoded><![CDATA[<p>That is a good point that I probably should have covered.  It does make my system less secure, but it does get rid of the errors that I have to read through in the logs.  I believe I am one of the few admins that actually cares enough to read through logs entirely without parsers and it takes a lot of time to do.  It also helps me optimize everything.  </p>
<p>Because of the time I spend reading through errors like this, I don&#8217;t really mind having a slightly more insecure system because I have full system backups, I limit user access, and I monitor for any modifications to files that are not within the /home directory.  So even if an exploit was discovered before I knew about it (it has happened once in the past 5 years), I&#8217;d still have everything repaired within 30 minutes of the initial exploit into my system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lloyd Kvam</title>
		<link>http://famousphil.com/blog/2010/04/nameds-working-directory-not-writeable/comment-page-1/#comment-1330</link>
		<dc:creator>Lloyd Kvam</dc:creator>
		<pubDate>Thu, 19 Aug 2010 13:35:34 +0000</pubDate>
		<guid isPermaLink="false">http://famousphil.com/?p=449#comment-1330</guid>
		<description>Are you sure that you really *want* named to be able to write to that directory?  Doesn&#039;t that allow exploits to wipe out your configuration and insert their own bogus configuration?

I realize your change gets rid of the log messages.  However, I think the &quot;fix&quot; makes your system less secure.</description>
		<content:encoded><![CDATA[<p>Are you sure that you really *want* named to be able to write to that directory?  Doesn&#8217;t that allow exploits to wipe out your configuration and insert their own bogus configuration?</p>
<p>I realize your change gets rid of the log messages.  However, I think the &#8220;fix&#8221; makes your system less secure.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Served from: famousphil.com @ 2012-05-19 13:11:59 by W3 Total Cache -->
