At 04:58 AM 9/29/2001 +0200, Samuele Pedroni wrote:
>Hi
>
> > *) Some opcodes will just not be available depending on the
> > characteristics you assign to the interpreter. File opens might be
> > forbidden, or code loading, or socket ops, or something. Settable as
> > needed by the interpreter creating the compartment.
>Yes but not every sensible op will be an opcode I presume ...
Probably not, but the list of ops is extendable at runtime. Any subroutine
that meets a few criteria can be an op function, and the compiler will turn
them into ops as it feels the need.
> > *) I've been thinking about having some sort of privilege system, but I'm
> > not sure it's appropriate. Might, though, if you want restricted
> > compartments to be able to create other restricted compartments.
>
>In that direction I think Java security has something one can borrow
>from, and with that 3rd party library can define new priviliges
>when needed that the user can grant/configure ...
I'll look into it. Sounds an awful lot like the VMS security system with a
few changes, so it'll probably fit into what's planned already.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
