Re: [IronPython] Re strict imports

fix but I'll have to talk to the DLR guys when I'm back from >> vacation on Thursday J >> >> >> >> *From:* [EMAIL PROTECTED] [mailto: >> [EMAIL PROTECTED] *On Behalf Of *Leo Carbajal >> *Sent:* Tuesday, September 02, 2008 9:06 PM >> >> *To:*

Re: [IronPython] Re strict imports

ilto: > [EMAIL PROTECTED] *On Behalf Of *Leo Carbajal > *Sent:* Tuesday, September 02, 2008 9:06 PM > > *To:* Discussion of IronPython > *Subject:* Re: [IronPython] Re strict imports > > > > The PAL stuff looks scary! Ok, not really, but I'll have to look at it when >

Re: [IronPython] Re strict imports

m back from vacation on Thursday :) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leo Carbajal Sent: Tuesday, September 02, 2008 9:06 PM To: Discussion of IronPython Subject: Re: [IronPython] Re strict imports The PAL stuff looks scary! Ok, not really, but I'll have to look

Re: [IronPython] Re strict imports

w > SecurityPermission(SecurityPermissionFlag.Execution)); should be sufficient > for what you're doing so far. > > > > Finally if you need to occasionally elevate permissions in your object > model you can mark your assembly as SecurityCritical and then have > individua

Re: [IronPython] Re strict imports

urface area by not having many public types other than the object model you're exposing. From: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> [mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>] On Behalf Of Leo Carbajal Sent: Tuesday, September 02, 2008 6:33 PM To: Discussion of

Re: [IronPython] Re strict imports

ant to restrict the surface area by not having many public > types other than the object model you're exposing. > > > > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *Leo Carbajal > *Sent:* Tuesday, September 02, 2008 6:33 PM > *To:* Discussi

Re: [IronPython] Re strict imports

TED] On Behalf Of Leo Carbajal Sent: Tuesday, September 02, 2008 6:33 PM To: Discussion of IronPython Subject: Re: [IronPython] Re strict imports Ok, so I think I misunderstood what a LinkDemand was, as well as the fact that the exception I'm getting is expected behavior. I added the [ass

Re: [IronPython] Re strict imports

Ok, so I think I misunderstood what a LinkDemand was, as well as the fact that the exception I'm getting is expected behavior. I added the [assembly: AllowPartiallyTrustedCallers] attribute to my assembly and now things work fine outside of the debug environment. From what I (now) understand, usin

Re: [IronPython] Re strict imports

This is a condensed version. You'll have to sign the assembly or you'll get an error at the domain creation step, other than that this should run just by starting a new console application, adding the IPY and DLR DLLs, and then copying and pasting this file over the default generated code. Even af

Re: [IronPython] Re strict imports

Do you have a simple reproduction that doesn't include any of your domain-specific code? On Tue, Sep 2, 2008 at 4:30 PM, Leo Carbajal <[EMAIL PROTECTED]> wrote: > So here's a strange wrinkle, > > when I run this with the debugger (unmodified except for adding the > IronPython assemblies as full-t

Re: [IronPython] Re strict imports

So here's a strange wrinkle, when I run this with the debugger (unmodified except for adding the IronPython assemblies as full-trust on the domain) it works fine and as expected. If I run it without the debugger attached it gives me the same exception as before, when I catch the exception myself I

Re: [IronPython] Re strict imports

ject: 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.

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 i

Re: [IronPython] Re strict imports

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 l

Re: [IronPython] Re strict imports

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 On Sat, Aug 23, 2008 at 9:44 PM, Michael Foord <[EMAIL PROTECTED]>wrote: > > > 2008/8/23 Dody Gunawinata <[EMAIL PROTECTED]> > >> >> http://l

Re: [IronPython] Re strict imports

fe.wmv [2] http://blog.secondlife.com/2006/05/05/microthreading-mono/ _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord Sent: Saturday, August 23, 2008 2:45 PM To: Discussion of IronPython Subject: Re: [IronPython] Re strict imports 2008/8/23 Dody Gunawinata <[EMAIL

Re: [IronPython] Re strict imports

2008/8/23 Dody Gunawinata <[EMAIL PROTECTED]> > > http://lists.ironpython.com/htdig.cgi/users-ironpython.com/2008-April/006765.html > Points to a bug in IronPython that is now fixed: http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=15928 > >

Re: [IronPython] Re strict imports

http://lists.ironpython.com/htdig.cgi/users-ironpython.com/2008-April/006765.html http://lists.ironpython.com/htdig.cgi/users-ironpython.com/2007-April/004740.html On Sat, Aug 23, 2008 at 3:32 PM, Michael Foord <[EMAIL PROTECTED]>wrote: > > > Search the mailing list archive on this issue. The bo

Re: [IronPython] Re strict imports

> Search the mailing list archive on this issue. The bottom line is, you > can't > - but there are tricks to make it more difficult. > Is that true? You can create an IronPython Engine in an AppDomain (IronPython 2 has lots of explicit support for this) and restrict the privileges of the AppDomai

Re: [IronPython] Re strict imports

Search the mailing list archive on this issue. The bottom line is, you can't - but there are tricks to make it more difficult. Dody G. On Fri, Aug 22, 2008 at 10:03 PM, Huzaifa <[EMAIL PROTECTED]> wrote: > > how can i restrict my user that he can not perform any imports or I/O > operations in th

[IronPython] Re strict imports

how can i restrict my user that he can not perform any imports or I/O operations in the script. -- View this message in context: http://www.nabble.com/Restrict-imports-tp19113682p19113682.html Sent from the IronPython mailing list archive at Nabble.com. _