<?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"
	>
<channel>
	<title>Comments for Useful Security</title>
	<atom:link href="http://www.usefulsecurity.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.usefulsecurity.com</link>
	<description>Solving real security problems that matter to real users</description>
	<pubDate>Thu, 11 Mar 2010 15:59:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>Comment on Apple Sandboxes Part 2 by Jabbering Giraffe &#187; sandbox(7)</title>
		<link>http://www.usefulsecurity.com/2007/11/apple-sandboxes-part-2/#comment-102</link>
		<dc:creator>Jabbering Giraffe &#187; sandbox(7)</dc:creator>
		<pubDate>Tue, 02 Jun 2009 20:17:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.usefulsecurity.com/?p=22#comment-102</guid>
		<description>[...] Apple Sandboxes Part 2 [...]</description>
		<content:encoded><![CDATA[<p>[...] Apple Sandboxes Part 2 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Sandboxes Part 1 by Jabbering Giraffe &#187; sandbox(7)</title>
		<link>http://www.usefulsecurity.com/2007/11/apple-sandboxes-part-1/#comment-101</link>
		<dc:creator>Jabbering Giraffe &#187; sandbox(7)</dc:creator>
		<pubDate>Tue, 02 Jun 2009 20:12:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.usefulsecurity.com/?p=21#comment-101</guid>
		<description>[...] Apple Sandboxes Part 1 [...]</description>
		<content:encoded><![CDATA[<p>[...] Apple Sandboxes Part 1 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Preventing Disclosure by c-had</title>
		<link>http://www.usefulsecurity.com/2007/08/preventing-disclosure/#comment-39</link>
		<dc:creator>c-had</dc:creator>
		<pubDate>Fri, 12 Sep 2008 03:18:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.usefulsecurity.com/?p=15#comment-39</guid>
		<description>Marcelo:
The example above does not place any requirements on the end user. Authentication is performed by the web application itself, and that web application controls access to its data. The point of the above is that I used SELinux to prevent any other web app from accessing this web app's private data.

Note that there are ways to utilize remote SELinux contexts between two cooperating SELinux systems, but they are not useful in your average web application due to that need to have cooperating systems. This is a much simpler example. If you're interested in using remote SELinux contexts between SELinux systems to enforce multi-system policies, I suggest you check out http://securityblog.org/brindle/2007/05/28/secure-networking-with-selinux/</description>
		<content:encoded><![CDATA[<p>Marcelo:<br />
The example above does not place any requirements on the end user. Authentication is performed by the web application itself, and that web application controls access to its data. The point of the above is that I used SELinux to prevent any other web app from accessing this web app&#8217;s private data.</p>
<p>Note that there are ways to utilize remote SELinux contexts between two cooperating SELinux systems, but they are not useful in your average web application due to that need to have cooperating systems. This is a much simpler example. If you&#8217;re interested in using remote SELinux contexts between SELinux systems to enforce multi-system policies, I suggest you check out <a href="http://securityblog.org/brindle/2007/05/28/secure-networking-with-selinux/" rel="nofollow">http://securityblog.org/brindle/2007/05/28/secure-networking-with-selinux/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Preventing Disclosure by Marcelo</title>
		<link>http://www.usefulsecurity.com/2007/08/preventing-disclosure/#comment-38</link>
		<dc:creator>Marcelo</dc:creator>
		<pubDate>Wed, 10 Sep 2008 13:22:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.usefulsecurity.com/?p=15#comment-38</guid>
		<description>I would like to know if, in order for this example to run properly, the web page user should also be running a system with SELinux, or it could be any client.
How, is the authentication done if the user is not using SELinux? How do you know his SecurityContext? Or you solved the authentication in a DAC way?
Thanks!</description>
		<content:encoded><![CDATA[<p>I would like to know if, in order for this example to run properly, the web page user should also be running a system with SELinux, or it could be any client.<br />
How, is the authentication done if the user is not using SELinux? How do you know his SecurityContext? Or you solved the authentication in a DAC way?<br />
Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Sandboxes Further Use by security and more &#187; more access control</title>
		<link>http://www.usefulsecurity.com/2008/06/apple-sandboxes-further-use/#comment-34</link>
		<dc:creator>security and more &#187; more access control</dc:creator>
		<pubDate>Mon, 30 Jun 2008 22:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.usefulsecurity.com/?p=24#comment-34</guid>
		<description>[...] McMillan and Chad Sellers have both some nice blog entries [2] due to the recent OS X trojaner: They both sign the need of more restrictive and finer grained [...]</description>
		<content:encoded><![CDATA[<p>[...] McMillan and Chad Sellers have both some nice blog entries [2] due to the recent OS X trojaner: They both sign the need of more restrictive and finer grained [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Sandboxes Part 1 by Mental Rootkit - OS X Malware</title>
		<link>http://www.usefulsecurity.com/2007/11/apple-sandboxes-part-1/#comment-33</link>
		<dc:creator>Mental Rootkit - OS X Malware</dc:creator>
		<pubDate>Thu, 26 Jun 2008 20:54:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.usefulsecurity.com/?p=21#comment-33</guid>
		<description>[...] sandbox policies he is referring to are the new security mechanisms in 10.5 based on the TrustedBSD project, a sister project to SELinux. Dino makes several other good [...]</description>
		<content:encoded><![CDATA[<p>[...] sandbox policies he is referring to are the new security mechanisms in 10.5 based on the TrustedBSD project, a sister project to SELinux. Dino makes several other good [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Sandboxes Part 1 by c-had</title>
		<link>http://www.usefulsecurity.com/2007/11/apple-sandboxes-part-1/#comment-29</link>
		<dc:creator>c-had</dc:creator>
		<pubDate>Fri, 07 Dec 2007 22:09:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.usefulsecurity.com/?p=21#comment-29</guid>
		<description>I don't think I quite understand your comment. Most user applications (including at least iTunes, QuickTime, and iLife) run as non-root users. If they're using Mach system calls, then they have the appropriate mach port rights to do so (note that Mach does not utilize the UNIX UID concept, but rather utilizes the Mach port capability system. More info here - http://developer.apple.com/documentation/Security/Conceptual/Security_Overview/Concepts/chapter_3_section_9.html).

More importantly, the new sandbox mechanism is an orthogonal mechanism to the current UNIX DAC model and the Mach port model, so sandbox policies can be applied (in a flexible way) regardless of whether the process is running as root. If you look at my examples in the second part of this post, those can be run as a regular user or as root and receive the same confinement. With sandboxes, root doesn't actually matter.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think I quite understand your comment. Most user applications (including at least iTunes, QuickTime, and iLife) run as non-root users. If they&#8217;re using Mach system calls, then they have the appropriate mach port rights to do so (note that Mach does not utilize the UNIX UID concept, but rather utilizes the Mach port capability system. More info here - <a href="http://developer.apple.com/documentation/Security/Conceptual/Security_Overview/Concepts/chapter_3_section_9.html" rel="nofollow">http://developer.apple.com/documentation/Security/Conceptual/Security_Overview/Concepts/chapter_3_section_9.html</a>).</p>
<p>More importantly, the new sandbox mechanism is an orthogonal mechanism to the current UNIX DAC model and the Mach port model, so sandbox policies can be applied (in a flexible way) regardless of whether the process is running as root. If you look at my examples in the second part of this post, those can be run as a regular user or as root and receive the same confinement. With sandboxes, root doesn&#8217;t actually matter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Sandboxes Part 1 by Joseph</title>
		<link>http://www.usefulsecurity.com/2007/11/apple-sandboxes-part-1/#comment-28</link>
		<dc:creator>Joseph</dc:creator>
		<pubDate>Fri, 07 Dec 2007 19:43:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.usefulsecurity.com/?p=21#comment-28</guid>
		<description>The reason apple has selected for an opt-in style of sandboxing is because much of the MACH related system calls expect to have root level access and since much of the OS and supported apps (include iTunes, QuickTime, iLife, ARD, etc) use the mac system and these "private api"s (which also expect root access) it would be impossible for Apple to roll this interface out as a required interface for at least 1 or 2 more OS releases from now.</description>
		<content:encoded><![CDATA[<p>The reason apple has selected for an opt-in style of sandboxing is because much of the MACH related system calls expect to have root level access and since much of the OS and supported apps (include iTunes, QuickTime, iLife, ARD, etc) use the mac system and these &#8220;private api&#8221;s (which also expect root access) it would be impossible for Apple to roll this interface out as a required interface for at least 1 or 2 more OS releases from now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Montavista Vision 2007 by c-had</title>
		<link>http://www.usefulsecurity.com/2007/10/montavista-vision-2007/#comment-6</link>
		<dc:creator>c-had</dc:creator>
		<pubDate>Thu, 11 Oct 2007 13:24:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.usefulsecurity.com/?p=19#comment-6</guid>
		<description>Thanks for the comment. We all really appreciate the work you guys are doing in Japan for SELinux on embedded devices. Anyone who wants to use SELinux in the embedded space will benefit. I personally am very grateful for the sebusybox work and all the modifications to the libraries and kernel (such as the improved read/write performance patches) to make embedded SELinux possible.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment. We all really appreciate the work you guys are doing in Japan for SELinux on embedded devices. Anyone who wants to use SELinux in the embedded space will benefit. I personally am very grateful for the sebusybox work and all the modifications to the libraries and kernel (such as the improved read/write performance patches) to make embedded SELinux possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Montavista Vision 2007 by Yuichi Nakamura</title>
		<link>http://www.usefulsecurity.com/2007/10/montavista-vision-2007/#comment-5</link>
		<dc:creator>Yuichi Nakamura</dc:creator>
		<pubDate>Thu, 11 Oct 2007 04:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.usefulsecurity.com/?p=19#comment-5</guid>
		<description>oops, woring -&#62; working ..</description>
		<content:encoded><![CDATA[<p>oops, woring -&gt; working ..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
