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

[J. Landman Gay]

On 9/5/03 4:35 AM, Robert Brenstein wrote:

> 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.

I've never come across a situation where a protected stack didn't just 
work without a need to unlock it. I don't protect too many stacks 
though, so my experience may be limited. What are you trying to do that 
would require unlocking the stack?

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com