<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Creating an AppDomain with limited permissions</title><link>http://blogs.msdn.com/shawnfa/archive/2004/10/25/247379.aspx</link><description>Oftentimes in an application, it's necessary to run untrusted code. The CLR lets you do this safely by placing the code in its own AppDomain and sandboxing the AppDomain to have a limited set of permissions. Usually setting up the AppDomain with the Internet</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Easily Creating a StrongNameMembershipCondition for an Assembly</title><link>http://blogs.msdn.com/shawnfa/archive/2004/10/25/247379.aspx#248115</link><pubDate>Tue, 26 Oct 2004 23:58:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:248115</guid><dc:creator>.Net Security Blog</dc:creator><description /></item><item><title>Easily Creating a StrongNameMembershipCondition for an Assembly</title><link>http://blogs.msdn.com/shawnfa/archive/2004/10/25/247379.aspx#248116</link><pubDate>Tue, 26 Oct 2004 23:58:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:248116</guid><dc:creator>.Net Security Blog</dc:creator><description /></item><item><title>re: Creating an AppDomain with limited permissions</title><link>http://blogs.msdn.com/shawnfa/archive/2004/10/25/247379.aspx#251036</link><pubDate>Tue, 02 Nov 2004 12:31:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:251036</guid><dc:creator>Kevin Westhead</dc:creator><description>Could you elaborate on why you would assign evidence to the AppDomain? In other words, how does it make the AppDomain more secure and what potential security holes does it plug that permission sets alone cannot?</description></item><item><title>An Enhanced Version of the Sandboxed AppDomain</title><link>http://blogs.msdn.com/shawnfa/archive/2004/10/25/247379.aspx#251241</link><pubDate>Tue, 02 Nov 2004 21:53:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:251241</guid><dc:creator>.Net Security Blog</dc:creator><description /></item><item><title>re: Creating an AppDomain with limited permissions</title><link>http://blogs.msdn.com/shawnfa/archive/2004/10/25/247379.aspx#251246</link><pubDate>Tue, 02 Nov 2004 19:08:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:251246</guid><dc:creator>Shawn</dc:creator><description>Hi Kevin,&lt;br&gt;&lt;br&gt;Good question ... I think I may turn this into a seperate post.  The easiest example of an instance where an AppDomain needs evidence assigned to it is the case where a web page is hosting some managed code.  In this case, the page might point at some code that lives on the local machine in the GAC, and therefore recieves a high level of trust.&lt;br&gt;&lt;br&gt;Now imagine that an exploit is found in this code, and by calling into a specific entry point, I can elevate my permissions and do whatever I want.  Now, if my web page doesn't load any code of its own, the only code on the callstack will be the buggy component in the application.  This means that if you don't take into account the AppDomain, an arbitrary web page can now exploit code sitting on my machine.&lt;br&gt;&lt;br&gt;Thankfully we do take the AppDomain into account, and all code hosted on a web page gets run in an AppDomain with a set of evidence that severly limits its permission grant.  For more information about that (from the other perspective) check out: &lt;a target="_new" href="http://blogs.msdn.com/shawnfa/archive/2003/06/26/57026.aspx"&gt;http://blogs.msdn.com/shawnfa/archive/2003/06/26/57026.aspx&lt;/a&gt;&lt;br&gt;&lt;br&gt;-Shawn</description></item><item><title>Peter Torr Provides More Details on Sandboxing AppDomains</title><link>http://blogs.msdn.com/shawnfa/archive/2004/10/25/247379.aspx#253973</link><pubDate>Mon, 08 Nov 2004 20:30:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:253973</guid><dc:creator>.Net Security Blog</dc:creator><description /></item><item><title>New and Notable 66</title><link>http://blogs.msdn.com/shawnfa/archive/2004/10/25/247379.aspx#267269</link><pubDate>Sat, 20 Nov 2004 20:12:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:267269</guid><dc:creator>Sam Gentile's Blog</dc:creator><description /></item><item><title>New and Notable 66</title><link>http://blogs.msdn.com/shawnfa/archive/2004/10/25/247379.aspx#267276</link><pubDate>Sat, 20 Nov 2004 20:13:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:267276</guid><dc:creator>Sam Gentile's Blog</dc:creator><description /></item><item><title>Don't Deny SkipVerification</title><link>http://blogs.msdn.com/shawnfa/archive/2004/10/25/247379.aspx#393757</link><pubDate>Fri, 11 Mar 2005 04:41:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:393757</guid><dc:creator>.Net Security Blog</dc:creator><description /></item><item><title>The Simple Sandboxing API</title><link>http://blogs.msdn.com/shawnfa/archive/2004/10/25/247379.aspx#449051</link><pubDate>Mon, 08 Aug 2005 20:04:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:449051</guid><dc:creator>.Net Security Blog</dc:creator><description>A while back I gave some sample code to show how to setup a sandboxed AppDomain.&amp;amp;amp;nbsp; This technique...</description></item></channel></rss>