On 5/26/05 7:16 PM, "Richard Gaskin" <[EMAIL PROTECTED]> wrote:
>> 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. ;) True, but turning it ON behind an app's back so that data can no longer be written to disk legitimately is what I'm more concerned about... Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] _______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
