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 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 AppDomain. Why would that not work? > > Michael > > > > > 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 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. > >> > >> _______________________________________________ > >> Users mailing list > >> [email protected] > >> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > >> > > > > > > > > -- > > nomadlife.org > > _______________________________________________ > > Users mailing list > > [email protected] > > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > > > > > -- > http://www.ironpythoninaction.com > _______________________________________________ > Users mailing list > [email protected] > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > -- nomadlife.org
_______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
