Security model for Perl with good support in Parrot (Safe/Opcode etc.)

2002-09-27 Thread Kv Org
I have always longed for a more flexible security system that could limit what a part of code could do in Perl. In perl5 Safe.pm (and Safe::Hole) have serious limitations and problems since it is difficult to have the security-limited code (that executes in a safe compartment) have use packages

RE: Security model for Perl with good support in Parrot (Safe/Opc ode etc.)

2002-10-04 Thread Kv Org
--- David Whipp <[EMAIL PROTECTED]> wrote: > Kv Org [mailto:[EMAIL PROTECTED]] wrote > > I believe Perl6 needs a facility to run > > "compartmented" code (object-oriented and > > module-loading) that is tagged as to its > permissions > > and "

RE: Security model for Perl with good support in Parrot (Safe/Opc ode etc.)

2002-10-04 Thread Kv Org
--- David Whipp <[EMAIL PROTECTED]> wrote: > Kv Org [mailto:[EMAIL PROTECTED]] wrote > > I believe Perl6 needs a facility to run > > "compartmented" code (object-oriented and > > module-loading) that is tagged as to its > permissions > > and "

Re: Draft sketch of bytecode generation

2002-10-30 Thread Kv Org
On Tue, 29 Oct 2002 09:55:23 -0800, Chromatic wrote: > >I'd really like to be able to save comments from >source files as metadata. This has at least two >potential benefits. First, it >makes it much easier >to recreate the whole file from bytecode (especially >refactored bytecode). >Second, it

Re: Securing Parrot ASM

2003-02-09 Thread Kv Org
I see two different situations when permissions/capabilities are concerned: the first is when one tries to run untrusted code, modules or parts of code and needs some kind of sanboxing mechanism. Safe has been built with this situation in mind, mostly. The second is when one builds a perl system w