Gordon Webster wrote:
Scanning the Transcript in stacks would not be useful
I feel, since it's true purpose could be so easily
obfuscated as Dar rightly points out. Also, encrypted
stacks would be a major headache.
I think that the 'sandbox' has to be at the bytecode
level to be truly effective and that means it would
probably be best to have this feature built into the
runtime engine.
I would imagine that this could work in much the same
way as the Java security layer that is the default
when running applets. Users would have the option to
run the stack in 'safe' mode which warns them what the
stack wants to do, instead of doing it.
The Java folk have 'been there, done that' so perhaps
the rev community could borrow from their experience
rather than reinventing the wheel.
We already have a secureMode property, and a spec has been provided for
a requested secureFolder property to help secureMode be useful.
Looking at RevOnline it appears that the concept of "trusted" sites has
already been implemented -- is it not documented?
--
Richard Gaskin
Fourth World Media Corporation
__________________________________________________
Rev tools and more: http://www.fourthworld.com/rev
_______________________________________________
use-revolution mailing list
[email protected]
http://lists.runrev.com/mailman/listinfo/use-revolution
