Reminder: objects cannot be copied when stack is password-protected!!! Even in a standalone. Grrrrrr....

[Josh Mellicker]

The saga continues:

Setting the passkey in the preOpenStack script (or other startup  
script) certainly allows a project (wherein objects need to be copied)  
to function normally. But now that preOpenStack messages get sent in  
the IDE in dp-5, I realize this technique of setting the passkey  
defeats part of the purpose of password-protecting a stack, since  
scripts can be viewed in the IDE (since simply opening the stack in  
the IDE unprotects it).

(It still does prevent the code from being read from disk by a text  
editor.)

Bottom line: To use the password property effectively in a project  
where objects need to be copied, there needs to be some kind of  
security check before setting the passkey.

Hope this helps someone down the line!


On Feb 26, 2008, at 3:32 PM, Josh Mellicker wrote:

> Once upon a time, a programmer was working on a project, with many  
> handlers that copy objects, for example, copy groups into groups to  
> form scrolling groups, and everything was working great, and the  
> programmer was very happy, and then, as a last step, he password  
> protected the stack, then, the next day...
>
> BLAMO!!!! Strange, bizarre things happened. Groups would not copy.  
> Death and destruction reigned. Monitors came crashing out windows.  
> Expletives burned the ears of innocent bystanders.
>
> This programmer then leapt off a cliff, ending it all.
>
>
> MORAL: If he had only put a single line of code:
>
> set the passkey of this stack to "swordfish"
>
> in the preOpenStack script, all would be fine.
>
>
> Please, tell your kids about "passkey", don't let them suffer a  
> similar fate!
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution