Protected stacks in 2.61 (was For goodness sake!)

[FlexibleLearning at aol.com]

Which neatly returns us to the crucial issues of  either re-introducing 
'clone' for template stacks etc in password  protected stack, AND/OR allowing 
runtime password protection to maintain  security.
 
MC IDE issues are preferential; 'broke' engine problems ain't.   :-)
 
/H
(Still has bee in bonnet)

> The first thing I always do when creating new stacks is to set  destroy 
> on for the reasons that Ken outlined plus password protection.  In fervor 
> of testing the cloning, I forgot to set it and was surprised  that 
> password protection was not working.
>
> Robert Brenstein

> In such a circumstance the only risk is  others using your machine during 
> the same MC session.  The  password is preserved on disk regardless of 
> the state of the  destroyStack property.
>
> Richard  Gaskin