Encrypted stack doesn't behave properly - oops; yes it does.

[Scott Rossi]

Recently, "Robert Brenstein"  wrote:

> But is it possible to unlock the stack for the duration of a given
> script only? Assume a handler that needs to do sth that requires a
> stack to be unlocked. It sets the passkey and does its business.
> However, it seems that this unlocks the stack until it is closed,
> thus opening it potentially for mischief. Is the a way to lock the
> stack back before the handler ends? It would be logical if setting a
> password did that trick, but does it?

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.

Regards,

Scott Rossi
Creative Director
Tactile Media, Multimedia & Design
-----
E: scott at tactilemedia.com
W: http://www.tactilemedia.com