On 5/26/05 3:42 PM, "Robert Brenstein" <[EMAIL PROTECTED]> wrote:
>> On 5/26/05 12:22 PM, "MisterX" <[EMAIL PROTECTED]> wrote: >> >>> Better question: >>> How can we prevent "any script" from setting this secure mode hell to true? >> >> Xavier has a point... a malicious stack could theoretically switch a stack >> that was not in secureMode into secureMode without telling anyone; the next >> time the application legitimately tries to write files, etc. it would >> prevent them from doing so - all that data entry would disappear. >> > > 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. 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
