<?xml version="1.0" encoding="UTF-8"?><!-- generator="lyceum/1.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Fedora 9 and Summit preview:  Confining the user with SELinux</title>
	<link>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/</link>
	<description>Red Hat Magazine</description>
	<pubDate>Sun,  7 Sep 2008 08:29:33 +0000</pubDate>
	<generator>http://lyceum.ibiblio.org/?v=1.0.2</generator>

	<item>
		<title>by: Dan Walsh</title>
		<link>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-116580</link>
		<pubDate>Thu, 14 Aug 2008 20:02:40 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-116580</guid>
					<description>We have hired a doc person who is working on updating all of the Fedora SELinux information.  So this should change.  All module changes should be carried forward r_file_perms still exists, even though the preferred method is read_file_perms. If you have a backward compatibility problems with your modules from one release to another that is a bug.  But Fedora is where we do our most active and fast paste development.  Red Hat Enterprise Linux is for slower more stable environment.  

I have never really supported strict policy and the move to a merge, I felt gave us the best bang for the buck.

</description>
		<content:encoded><![CDATA[<p>We have hired a doc person who is working on updating all of the Fedora SELinux information.  So this should change.  All module changes should be carried forward r_file_perms still exists, even though the preferred method is read_file_perms. If you have a backward compatibility problems with your modules from one release to another that is a bug.  But Fedora is where we do our most active and fast paste development.  Red Hat Enterprise Linux is for slower more stable environment.  </p>
<p>I have never really supported strict policy and the move to a merge, I felt gave us the best bang for the buck.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ganesh Neupane</title>
		<link>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-115035</link>
		<pubDate>Wed, 13 Aug 2008 05:06:59 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-115035</guid>
					<description>One of the great trekking to do before you dies:
 
Mt. Everest, standing mightily at 8848m. Are the World's highest peak and the ultimate Himalayan dream for many trekkers. Everest trek (with more time for acclimatization) enables you not only to witness Mount Everest but also the 4th &#38; 5th highest peaks. Lhote at 8516m., Makalu 8467m., as well as numerous other giant peaks. This region is truly the roof of the World. 
Besides, trek goes through the heartland of the Sherpa (Mountain peoples) who are of Tibet origin and passes numerous charming villages, many with picturesque gompas that are spectacularly set amidst its mountainous surrounding. Before reaching the Everest Base camp, the trail follows the Khumbu Glacier with huge ice pinnacles soaring to unbelievable height. 
Fly to Lukla and following the Dhuda Koshi river valley through beautiful pine and rhododendron trees. The jagged, Icy &#38; snow capped peaks of Thamseku 6623m. &#38; Kushum Kanguru 6369m, tower above the trail. A steep climb then leads us to Namche Bazaar 3345m. Were we taking our first stop for rest (Acclimatization). Get way of Everest Base camp or Everest region for adventure trekking or climbing any peaks.
On the trail to Thyanboche, those with a keen eye will be rewarded with sightings of musk deer, thar (Mountain goat) Impeyan Pheasant. Thyangboche monastery is set in a beautiful location with chortens adorned with player flags and mani walls a constant remainder of the local Buddhist cultural. Views of Mt. Everest 8848m., Lhotse 8516m.,Ama Dablam 6856m, Thamserku 6623m., Kangtenga 6779m., as well as many tiny mountain in this region.
 
Ganesh Neupane
Monterosa Treks and Expedition
mail: monte@mos.com.np
http://www.monterosa-nepal.com
</description>
		<content:encoded><![CDATA[<p>One of the great trekking to do before you dies:</p>
<p>Mt. Everest, standing mightily at 8848m. Are the World&#8217;s highest peak and the ultimate Himalayan dream for many trekkers. Everest trek (with more time for acclimatization) enables you not only to witness Mount Everest but also the 4th &amp; 5th highest peaks. Lhote at 8516m., Makalu 8467m., as well as numerous other giant peaks. This region is truly the roof of the World.<br />
Besides, trek goes through the heartland of the Sherpa (Mountain peoples) who are of Tibet origin and passes numerous charming villages, many with picturesque gompas that are spectacularly set amidst its mountainous surrounding. Before reaching the Everest Base camp, the trail follows the Khumbu Glacier with huge ice pinnacles soaring to unbelievable height.<br />
Fly to Lukla and following the Dhuda Koshi river valley through beautiful pine and rhododendron trees. The jagged, Icy &amp; snow capped peaks of Thamseku 6623m. &amp; Kushum Kanguru 6369m, tower above the trail. A steep climb then leads us to Namche Bazaar 3345m. Were we taking our first stop for rest (Acclimatization). Get way of Everest Base camp or Everest region for adventure trekking or climbing any peaks.<br />
On the trail to Thyanboche, those with a keen eye will be rewarded with sightings of musk deer, thar (Mountain goat) Impeyan Pheasant. Thyangboche monastery is set in a beautiful location with chortens adorned with player flags and mani walls a constant remainder of the local Buddhist cultural. Views of Mt. Everest 8848m., Lhotse 8516m.,Ama Dablam 6856m, Thamserku 6623m., Kangtenga 6779m., as well as many tiny mountain in this region.</p>
<p>Ganesh Neupane<br />
Monterosa Treks and Expedition<br />
mail: <a href="mailto:monte@mos.com.np">monte@mos.com.np</a><br />
<a href="http://www.monterosa-nepal.com" rel="nofollow">http://www.monterosa-nepal.com</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Aleksander Adamowski</title>
		<link>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-114584</link>
		<pubDate>Mon, 11 Aug 2008 23:52:06 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-114584</guid>
					<description>The "removal of unconfined.pp" idea is from an interview with your own self (http://fedoraproject.org/wiki/Interviews/SELinux):

"So in Fedora 8 you can setup login users to be user_t, staff_t and they can reach sysadm_t, just like in strict policy. The default user account will remain unconfined. If you want to remove the ability to run unconfined processes you can just remove the unconfined module. "semodule -r unconfined"."

I didn't get the memo that it is no longer kosher in Fedora 9.

The fact is, it's very hard to scrap together consistent knowledge about changes in SELinux in consecutive Fedora releases.

It's extremely difficult to track all those changes that break backward compatibility with my custom SELinux modules. I have to gather it from all around the web (your LJ blog, interviews and Red Hat magazine articles, the mailing list and so on). The object permission macros are changing (e.g. r_file_perms -&#62; read file perms), domains come and go, tools change in behaviour, and there's no single place to track those - only by trial and error (when something breaks).

Ideally it should be in the release notes for Fedora, but the SELinux section usually contains some canned information that comprises only links to trivial, incomplete or outdated information, e.g.:

http://docs.fedoraproject.org/release-notes/f8/en_US/sn-Security.html#SELinux

http://docs.fedoraproject.org/release-notes/f9/en_US/sn-Security.html#SELinux

Note that these release notes sections are identical; the last link leads to documentation that has stopped being updated in the FC5 era.
</description>
		<content:encoded><![CDATA[<p>The &#8220;removal of unconfined.pp&#8221; idea is from an interview with your own self (http://fedoraproject.org/wiki/Interviews/SELinux):</p>
<p>&#8220;So in Fedora 8 you can setup login users to be user_t, staff_t and they can reach sysadm_t, just like in strict policy. The default user account will remain unconfined. If you want to remove the ability to run unconfined processes you can just remove the unconfined module. &#8220;semodule -r unconfined&#8221;.&#8221;</p>
<p>I didn&#8217;t get the memo that it is no longer kosher in Fedora 9.</p>
<p>The fact is, it&#8217;s very hard to scrap together consistent knowledge about changes in SELinux in consecutive Fedora releases.</p>
<p>It&#8217;s extremely difficult to track all those changes that break backward compatibility with my custom SELinux modules. I have to gather it from all around the web (your LJ blog, interviews and Red Hat magazine articles, the mailing list and so on). The object permission macros are changing (e.g. r_file_perms -&gt; read file perms), domains come and go, tools change in behaviour, and there&#8217;s no single place to track those - only by trial and error (when something breaks).</p>
<p>Ideally it should be in the release notes for Fedora, but the SELinux section usually contains some canned information that comprises only links to trivial, incomplete or outdated information, e.g.:</p>
<p><a href="http://docs.fedoraproject.org/release-notes/f8/en_US/sn-Security.html#SELinux" rel="nofollow">http://docs.fedoraproject.org/release-notes/f8/en_US/sn-Security.html#SELinux</a></p>
<p><a href="http://docs.fedoraproject.org/release-notes/f9/en_US/sn-Security.html#SELinux" rel="nofollow">http://docs.fedoraproject.org/release-notes/f9/en_US/sn-Security.html#SELinux</a></p>
<p>Note that these release notes sections are identical; the last link leads to documentation that has stopped being updated in the FC5 era.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dan Walsh</title>
		<link>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-114432</link>
		<pubDate>Mon, 11 Aug 2008 14:50:46 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-114432</guid>
					<description>I am not a big fan of sysadm_t,  I call it the drunken unconfined_t, it can pretty much do anything on the system it wants but stumbles around a lot.  So I would not advise removing the unconfined.pp file.   I have no idea why it would not be logging to /var/log/audit/audit.log

I tried running screen from sysadm_r:sysadm_t on Fedora 9 and it seems to work.
</description>
		<content:encoded><![CDATA[<p>I am not a big fan of sysadm_t,  I call it the drunken unconfined_t, it can pretty much do anything on the system it wants but stumbles around a lot.  So I would not advise removing the unconfined.pp file.   I have no idea why it would not be logging to /var/log/audit/audit.log</p>
<p>I tried running screen from sysadm_r:sysadm_t on Fedora 9 and it seems to work.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Aleksander Adamowski</title>
		<link>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-111917</link>
		<pubDate>Fri, 08 Aug 2008 14:10:30 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-111917</guid>
					<description>After unloading the unconfined module on Fedora 8, I cannot launch screen from the root account:

# screen
-bash: /usr/bin/screen: Permission denied

What's funny, nothing is logged even when I disable dontaudit globally using "semodule -DB". When I "setenforce 0", screen launches fine.

What's even funnier, I were able to get screen working for unprivileged users after mapping them to user_u using _default_.

So now, although I have the most privileged context of root:system_r:sysadm_t, I cannot launch screen like the unprivileged users can.
</description>
		<content:encoded><![CDATA[<p>After unloading the unconfined module on Fedora 8, I cannot launch screen from the root account:</p>
<p># screen<br />
-bash: /usr/bin/screen: Permission denied</p>
<p>What&#8217;s funny, nothing is logged even when I disable dontaudit globally using &#8220;semodule -DB&#8221;. When I &#8220;setenforce 0&#8243;, screen launches fine.</p>
<p>What&#8217;s even funnier, I were able to get screen working for unprivileged users after mapping them to user_u using _default_.</p>
<p>So now, although I have the most privileged context of root:system_r:sysadm_t, I cannot launch screen like the unprivileged users can.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ericdes</title>
		<link>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-110060</link>
		<pubDate>Wed, 30 Jul 2008 14:48:38 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-110060</guid>
					<description>Thank you, it's working now.</description>
		<content:encoded><![CDATA[<p>Thank you, it&#8217;s working now.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dan Walsh</title>
		<link>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-110036</link>
		<pubDate>Wed, 30 Jul 2008 13:00:06 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-110036</guid>
					<description>Try:

# semanage login -m -s user_u -r s0 __default__

__default__ currently has an MCS/MLS range of s0-s0:c0.c1023
but the user_u SELinux user is only allowed to use s0.

</description>
		<content:encoded><![CDATA[<p>Try:</p>
<p># semanage login -m -s user_u -r s0 __default__</p>
<p>__default__ currently has an MCS/MLS range of s0-s0:c0.c1023<br />
but the user_u SELinux user is only allowed to use s0.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ericdes</title>
		<link>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-109984</link>
		<pubDate>Wed, 30 Jul 2008 09:01:40 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-109984</guid>
					<description>semanage login -m -s user_u __default__
leads to this error message:
------------------------------
libsemanage.validate_handler: MLS range s0-s0:c0.c1023 for Unix user __default__ exceeds allowed range s0 for SELinux user user_u (No such file or directory).
libsemanage.validate_handler: seuser mapping [__default__ -&#62; (user_u, s0-s0:c0.c1023)] is invalid (No such file or directory).
libsemanage.dbase_llist_iterate: could not iterate over records (No such file or directory).
/usr/sbin/semanage: Could not modify login mapping for __default__
------------------------------

Any idea why it fails?</description>
		<content:encoded><![CDATA[<p>semanage login -m -s user_u __default__<br />
leads to this error message:<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
libsemanage.validate_handler: MLS range s0-s0:c0.c1023 for Unix user __default__ exceeds allowed range s0 for SELinux user user_u (No such file or directory).<br />
libsemanage.validate_handler: seuser mapping [__default__ -&gt; (user_u, s0-s0:c0.c1023)] is invalid (No such file or directory).<br />
libsemanage.dbase_llist_iterate: could not iterate over records (No such file or directory).<br />
/usr/sbin/semanage: Could not modify login mapping for __default__<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>Any idea why it fails?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: qjfselenfa</title>
		<link>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-107597</link>
		<pubDate>Mon, 21 Jul 2008 23:27:10 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-107597</guid>
					<description>Hello my friend, your site is very good! &lt;a href="http://xmsubdjptympn.com" rel="nofollow"&gt;http://xmsubdjptympn.com&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Hello my friend, your site is very good! <a href="http://xmsubdjptympn.com" rel="nofollow">http://xmsubdjptympn.com</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dan Walsh</title>
		<link>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-105339</link>
		<pubDate>Fri, 11 Jul 2008 12:41:58 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2008/04/17/fedora-9-and-summit-preview-confining-the-user-with-selinux/#comment-105339</guid>
					<description>Basavraj, please contact me on the Fedora-list or directly with questions on SELinux.  I would need to know more about what problems you are having and how you would like to confine your users.</description>
		<content:encoded><![CDATA[<p>Basavraj, please contact me on the Fedora-list or directly with questions on SELinux.  I would need to know more about what problems you are having and how you would like to confine your users.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
