Encryption for file vs Standalone App

[trevix]

Thanks, probably the only solution.
Hard perhaps because of the need to do this operation so many time and pinpoint all the scripts that need the unlock (in my case at least)

[trevix]

Actually, reading from the dictionary about password:

After setting the password the password protection does not take effect until the stack has been removed from memory and reloaded.

Removing and reloading makes this method a little cumbersome

Trevix

[jacque]

What features do your users need? If they don't need access to the scripts then you may be able to just set the password once and forget about it. The only other restriction besides script access is copying objects.

[trevix]

My App need to do cloning and copying of objects, stacks, cards, with repeated saving and drag/drop.
It is an App based on templates and stacks that run using those templates. It won't run with script passworded.

Anyway, as i mentioned here (http://forums.livecode.com/viewtopic.ph ... 37#p152137) it is easy to cheat a protected stack if passkeyied by its App: open it with the IDE and paste some code on a new object.
Also the passkey is a one way: once unlocked by script, you cannot relock it by script.See BUG 546

I may have to resort to encrypt and decrypt.
But since LC is supposed to be able to easily create commercial Apps, with a minimum reasonable protection, I think LC has to grow a lot more, in this sense.

Regards
Trevix

[jacque]

One option might be to move all the working scripts into the standalone and put it in use when it launches. The template stacks would have only the barest framework required to run. That way the app stack can always remain protected and you wouldn't need to protect the template stacks at all. I've done this with very large projects that run multiple template-based stacks and it works well.