Re: Password protecting a stack in the distribution
Same problem here trying to encrypt my library (to be used on on-Rev server). Livecode 4,6,3 on Mac (4,6,4 not tested now). My problem is now solved (see second try) but the workflow is not straightforward. First try (does'nt work: - Main stack (splash screen) and my library (start using as it does). - standalone app settings: - main stack: encrypt with password - add stack file: my library, encrypt with password - Result: no encryption of my library (found in the pack - contents/MacOs/myLib.livecode Second try (was successful): - Main stack and myLib as substack - standalone app settings: - main stack: - check move substack into individual stackfiles - create folder for this stack (jc) - encrypt with password (for both main stack and myLib) - Result: nin the folder found in the pack - contents/MacOs/jc there is a file myLib.rev (rev???) which is encrypted (to verify: open myLib.rev with TextEdit, or open a script in Livecode). Why is it so tortuous to only encrypt a library? Jacques 2011/9/11 Andrew Henshaw hens...@me.com Hi, Im wondering if anyone can shed some light on the best way to do this! I have built a library stack which Im including in the distribution and selected the 'encrypt with password' option for both the main stack, and this library stack, however when I compile if I go into the package the .rev file is there with clear text contents, totally readable. Ive also tried using the set the password of this stack to mypassword and then saved the stack and re-loaded it and that does encrypt the original stack and ask for a password before I can edit it, but for some reason when I compile again the stack is put into the distribution in clear text again. Any ideas or other ways of doing this? Andy ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Password protecting a stack in the distribution
Hi, Im wondering if anyone can shed some light on the best way to do this! I have built a library stack which Im including in the distribution and selected the 'encrypt with password' option for both the main stack, and this library stack, however when I compile if I go into the package the .rev file is there with clear text contents, totally readable. Ive also tried using the set the password of this stack to mypassword and then saved the stack and re-loaded it and that does encrypt the original stack and ask for a password before I can edit it, but for some reason when I compile again the stack is put into the distribution in clear text again. Any ideas or other ways of doing this? Andy ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Password protecting a stack in the distribution
On 9/11/11 4:17 AM, Andrew Henshaw wrote: Hi, Im wondering if anyone can shed some light on the best way to do this! I have built a library stack which Im including in the distribution and selected the 'encrypt with password' option for both the main stack, and this library stack, however when I compile if I go into the package the .rev file is there with clear text contents, totally readable. Ive also tried using the set the password of this stack to mypassword and then saved the stack and re-loaded it and that does encrypt the original stack and ask for a password before I can edit it, but for some reason when I compile again the stack is put into the distribution in clear text again. I haven't seen that happen, so something odd is going on. When I set a password manually, it always sticks. But try setting the password on the stack manually and don't set it in the standalone builder. If you are including it in the Copy Files pane, I'm not sure the SB will do anything other than just move it next to the engine, so try handling the protection yourself. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
