ReSet passkey (was "For xxx sake!")

[Robert Brenstein]

>So what's the next step? How easily/quickly can Tuv (?) close the  loophole
>that has been created in 2.6.1 so "clone" (and other commands that  have now
>been disabled) can be made to work again in a protected stack? I am  assuming
>bribary is allowed?

I guess vote for bug 546 :) As you can see from its number, it has 
been entered a long long time ago. If enough people vote on it, may 
be it will be addressed. Technically, does not seem much work for me 
since most of the code is already there.

>And what's the workaround to allow 2.6.1 users access the features in  a
>protected stack with these requirements?

I guess the only way is to close and reopen stack if that does not 
mess things up for you.

Robert