The CLR doesn't dump out full exception information on SecurityExceptions in partial trust - you can get a lot more information if you look at the exception in a debugger, or if you Assert for FullTrust before doing a ToString on the permission. Once you do that, you should be able to get more data including the demanded permission and the assembly which caused the demand to fail, instead of the message saying "The granted set of the failing assembly was:" which does not say which assembly is causing the problem.
Also, can you try adding IronPython.dll and IronPython.Modules.dll to the fullTrustAssemblies argument to AppDomain.CreateDomain<http://msdn.microsoft.com/en-us/library/ms130766.aspx>? Thanks, Shri From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leo Carbajal Sent: Sunday, August 31, 2008 10:59 PM To: Discussion of IronPython Subject: Re: [IronPython] Re strict imports I hate bringing this issue up over and over again, but anyway, I'd rather re-use one of these conversations. This CAS stuff is really driving me nuts, moreso because it makes me feel dumber than a door nail to not understand what's going on. I've got IPY 2.0 loading into a 'sandboxed' domain, and it can run basic python calculations and stuff like print just fine, the moment I try to have it interact with an object I pass in through globals though I get a permission error where (it looks like to me) the act is asking for nothing less than completely unrestricted access. Here's the error: Unhandled Exception: System.Security.SecurityException: Request failed. at _stub_$6##6(Closure , CallSite , Object , CodeContext ) at _stub_MatchCaller(Object , CallSite , Object[] ) at System.Scripting.Actions.CallSite`1.UpdateAndExecute(Object[] args) at System.Scripting.Actions.UpdateDelegates.Update2[T,T0,T1,TRet](CallSite site, T0 arg0, T1 arg1) at B:\Code\IronPythonShell\IronPythonShell\bin\Debug\script2.py$1##1(Closure, Scope , LanguageContext ) at System.Scripting.Runtime.OptimizedScriptCode.InvokeTarget(LambdaExpression code, Scope scope) at System.Scripting.SourceUnit.Execute(Scope scope, ErrorSink errorSink) at Microsoft.Scripting.Hosting.ScriptSource.Execute(ScriptScope scope) at Microsoft.Scripting.Hosting.ScriptRuntime.ExecuteFile(String path) at Microsoft.Scripting.Hosting.ScriptRuntime.ExecuteFile(String path) at IronPythonShell.Program.Main(String[] args) in B:\Code\IronPythonShell\Iro nPythonShell\Program.cs:line 49 The action that failed was: Demand The type of the first permission that failed was: System.Security.PermissionSet The demand was for: <PermissionSet class="System.Security.PermissionSet" version="1" Unrestricted="true"/> The granted set of the failing assembly was: <PermissionSet class="System.Security.PermissionSet" version="1"> <IPermission class="System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0<http://2.0.0.0>, Culture=neutral, PublicKeyToken=b77a5c561934e089" version="1" Read="B:\Code\IronPythonShell\IronPythonShell\bin\Debug\" PathDiscovery="B:\Code\IronPythonShell\IronPythonShell\bin\Debug\"/> <IPermission class="System.Security.Permissions.ReflectionPermission, mscorlib, Version=2.0.0.0<http://2.0.0.0>, Culture=neutral, PublicKeyToken=b77a5c561934e089" version="1" Unrestricted="true"/> <IPermission class="System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0<http://2.0.0.0>, Culture=neutral, PublicKeyToken=b77a5c561934e089" version="1" Unrestricted="true"/> </PermissionSet> The code looks like this: Item item = new Item("Monkey"); item.Value = 10; item.Type = ItemType.Misc; PermissionSet pset = new PermissionSet(PermissionState.None); pset.AddPermission(new SecurityPermission(PermissionState.Unrestricted)); pset.AddPermission(new ReflectionPermission(PermissionState.Unrestricted)); pset.AddPermission(new FileIOPermission(FileIOPermissionAccess.PathDiscovery | FileIOPermissionAccess.Read, AppDomain.CurrentDomain.BaseDirectory)); AppDomainSetup domainSetup = new AppDomainSetup(); domainSetup.ApplicationBase = AppDomain.CurrentDomain.BaseDirectory; // create the sandboxed domain AppDomain sandbox = AppDomain.CreateDomain( "Sandboxed Domain", AppDomain.CurrentDomain.Evidence, domainSetup, pset, CreateStrongName(Assembly.GetExecutingAssembly()), CreateStrongName(Assembly.GetAssembly(typeof(ScriptRuntime))), CreateStrongName(Assembly.GetAssembly(typeof(System.Scripting.ScriptCode)))); ScriptRuntime runtime = ScriptRuntime.Create(sandbox); runtime.Globals.SetVariable("Artifact", new ScriptableItem(item)); runtime.ExecuteFile(Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "script2.py")); Script2.py: import Artifact i = 200 while i > 0: i = i - 1 print "Done in the second verse. Yes?" print Artifact.Name Item and ScriptableItem are simple classes with only those two properties, ScriptableItem inherits from MarshalByRefObject. The idea is that Item will eventually be a very powerful class and ScriptableItem is a wrapper around it to only provide access to certain portions of the class (IPY 1.1 didn't do so well with obeying interfaces). I tried using [EnvironmentPermissionAttribute(SecurityAction.LinkDemand, Unrestricted = true)] on both of those classes, but it didn't work. CreateStrongName is a method I pulled from this post: http://blogs.msdn.com/shawnfa/archive/2005/08/08/449050.aspx The way I understand it, Microsoft.Scripting, Microsoft.Scripting.Core and my own assembly should be given full trust when the sandbox domain is first created so I'm at a complete loss. This code works fine, of course, if I don't create the runtime in the domain. A little light, or some more reference material, would be very helpful =\ --- LC On Mon, Aug 25, 2008 at 12:56 PM, Michael Foord <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: Dody Gunawinata wrote: Ah, my knowledge is out of date then. I think the more apt thread is here http://lists.ironpython.com/htdig.cgi/users-ironpython.com/2008-June/007523.html Yep - Dino confirming that sandboxing is one of the intended uses of IronPython and that it should work (and a link to a blog entry about why some sandboxing problems are very difficult - particularly server applications where you need to protect against DoS through CPU and memory over use). Michael
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
