>> I don't believe this is an issue. Rev loads a stack into memory before >> running, and it doesn't save anything to the drive until you tell it to do >> so. Thus if your stack was password protected on the drive, it will stay >> that way until you save it without a password. >> >> Also, keep in mind that setting a passkey allows you to edit scripts until >> the stack is closed; it does not remove the password from the stack.
> Yes, all true but that was not my issue. > > Take 2. Is it possible to unlock the stack for the duration of a > given script only? In other words, is it possible to restore locked > state without closing the stack? I don't think so. I have tested a > number of options and can't seem to be able to relock the stack once > it is unlocked. > > The issue is that once the passkey is set, the scripts are no longer > protected. This means that a user may see what they may not be > supposed to see. Remember that password protecting the stack has been > advocated here not only to protect scripts but also sensitive data. > However, dynamic scripting usually requires unlocking the stack to > succeed. > > Since setting password to empty removes protection, a logical > extension would be that setting passkey to empty relocks the stack. I > have just entered this into bugzilla as a suggestion (#546). Are you planning to distribute a script editor with your stacks? Through what means can a user gain access to your scripts? Regards, Scott Rossi Creative Director Tactile Media, Multimedia & Design ----- E: [EMAIL PROTECTED] W: http://www.tactilemedia.com _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
