Encryption of Saved Stack of Standalone (Linux)
dcragg at lacscentre.co.uk
Tue Feb 3 14:18:31 CST 2004
At 12:57 pm -0700 3/2/04, Dar Scott wrote:
>On Tuesday, February 3, 2004, at 12:52 PM, Bojsza wrote:
>> It doesn't have to be the same password. I just want to have the
>>stacks that are created by a standalone to be encrypted. So, if I
>>placed a password field with a password in it and had that placed
>>in the stack that is part of the distribution build can it be used
>>to encrypt any stacks created?
>I would think so. However, you might not want to bother with the
>field. You might want to use a custom property or just "hardwire"
>it into the script.
Hardwiring in the script is probably safest as you can still access
custom properties and fields in a password-protected stack (although
you can't read them casually in a text editor).
After cloning the stack and setting its name, something like this:
if the password of stack "myNewStack" is empty then
set the password of stack "myNewStack" to "bigsecret"
Then save the stack.
More information about the use-livecode