Thanks Curt for the repro and stack trace and thanks Sho for the original report. This is definitely a bug - we're using reflection to load an internal type in the remote domain and instead we could do it non-reflectively and avoid the security check.
I've opened a bug (http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=15928) for this - it shouldn't be too hard to fix but there's a few things in the queue first. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curt Hagenlocher Sent: Tuesday, April 01, 2008 5:17 PM To: Discussion of IronPython Subject: Re: [IronPython] Restricting IronPython/DLR in a Sandbox? For what it's worth, I got that result on 2.0.50727.1434. On Tue, Apr 1, 2008 at 3:52 PM, Sho List <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: Thanks Curt, that code does reproduce the exception I am getting. I am running on 2.0.50727.312 Thanks! ________________________________ More immediate than e-mail? Get instant access with Windows Live Messenger.<http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_instantaccess_042008> _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
