For goodness sake!

[Robert Brenstein]

>Hi Klaus,
>
>Not entirely true. v2.5 prohibited "set/get script" and  "copy [obj]" in
>password protected stacks, but "clone" has always been  available.
>
>My points:
>[1] I can appreciate protecting script and  copying access to prevent
>circumventing protected stacks, but "clone" can do  nothing except 
>duplicate in the
>same environment.

bugzilla this !

I am still not clear, though, if your errors occur in 
password-protected stacks that are locked or unlocked. May be I 
missed a post. I will need this to work soon, so I'd like to test it 
out.

>[2] If dynamic  scripting in protected stacks is being 'phased out', we need
>to be able to  unlock, do whatever, then *re-set* the protection. This last
>step is not  available, and until 2.5 was not required. Not only should it now
>be available,  but it has become a CRITICAL command.

vote for bug 546 :)

Robert