Ken Ray wrote:
On 5/26/05 3:42 PM, "Robert Brenstein" <[EMAIL PROTECTED]> wrote:
Didn't Jacque say that you have to actually relaunch in order to
activate the secureMode change? That should prevent the thing you
worry about.
Yes, but only once it has been *set*. If an application launches and
*doesn't* set the secureMode, then opens a malicious stack that *sets* the
secureMode, you won't be able to set it back until the next restart, and not
knowing it has been set would cause the problems I mention above.
Turning OFF the ability to write damaging files to the user's system
seems the least of our concerns. ;)
--
Richard Gaskin
Fourth World Media Corporation
___________________________________________________________
[EMAIL PROTECTED] http://www.FourthWorld.com
_______________________________________________
use-revolution mailing list
[email protected]
http://lists.runrev.com/mailman/listinfo/use-revolution
