<?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: Ownership of the Local SE Linux Policy</title>
	<atom:link href="http://etbe.coker.com.au/2008/08/19/ownership-local-se-linux-policy/feed/" rel="self" type="application/rss+xml" />
	<link>http://etbe.coker.com.au/2008/08/19/ownership-local-se-linux-policy/</link>
	<description>Linux, politics, and other interesting things</description>
	<lastBuildDate>Thu, 09 Feb 2012 01:09:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: etbe</title>
		<link>http://etbe.coker.com.au/2008/08/19/ownership-local-se-linux-policy/comment-page-1/#comment-15404</link>
		<dc:creator>etbe</dc:creator>
		<pubDate>Wed, 20 Aug 2008 11:23:04 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=715#comment-15404</guid>
		<description>http://algebraicthunk.net/~dburrows/blog/entry/package-management-sudoku/

It had idly occurred to me that as a result of my comment about Sudoku someone might try to modify Apt to give it the capability to solve such problems.  It did not occur to me that Apt might already be able to solve such problems until I read the blog post at the above URL.</description>
		<content:encoded><![CDATA[<p><a href="http://algebraicthunk.net/~dburrows/blog/entry/package-management-sudoku/" rel="nofollow">http://algebraicthunk.net/~dburrows/blog/entry/package-management-sudoku/</a></p>
<p>It had idly occurred to me that as a result of my comment about Sudoku someone might try to modify Apt to give it the capability to solve such problems.  It did not occur to me that Apt might already be able to solve such problems until I read the blog post at the above URL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: etbe</title>
		<link>http://etbe.coker.com.au/2008/08/19/ownership-local-se-linux-policy/comment-page-1/#comment-15397</link>
		<dc:creator>etbe</dc:creator>
		<pubDate>Wed, 20 Aug 2008 03:27:31 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=715#comment-15397</guid>
		<description>Anon: Of course you could just run that daemon as unconfined_t and run other daemons in confined domains.</description>
		<content:encoded><![CDATA[<p>Anon: Of course you could just run that daemon as unconfined_t and run other daemons in confined domains.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://etbe.coker.com.au/2008/08/19/ownership-local-se-linux-policy/comment-page-1/#comment-15392</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 19 Aug 2008 23:06:54 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=715#comment-15392</guid>
		<description>I avoid SELinux on systems I administrate precisely because using it will require me to write at least some of my own local policies.  For example, if I want to set up a daemon running on data in /srv/subdomain.mydomain.org , I&#039;ll have to give it explicit access to that directory, beyond normal UNIX permissions.</description>
		<content:encoded><![CDATA[<p>I avoid SELinux on systems I administrate precisely because using it will require me to write at least some of my own local policies.  For example, if I want to set up a daemon running on data in /srv/subdomain.mydomain.org , I&#8217;ll have to give it explicit access to that directory, beyond normal UNIX permissions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

