Bonsoir Ted, Bill et Mark,
Just an add-up to this thread with an email I posted to the Improve
list less than a week ago:
I work every day with protected stacks and here is the way I make
my life easy with them:
I have a text file with a list of passwords and stack names in it.
At every stack (or substack) preOpenStack I have a routine in a
library that checks if this file exists, parse it and set the
passkey accordingly.
In distribution, this file of course is not included and, in
addition, the routine is skipped when the environment is not 'Dev'
then all stacks stay protected.
But in my 'Dev' environment, I am never prompted to enter any PW.
Le 1 oct. 08 à 18:45, Mark Schonewille a écrit :
When you set a password, all your scripts are encrypted. When a
stack opens, either in Revolution or in a standalone, the scripts
are decrypted. However, there is no way to see the scripts in the
open stack and when you save the stack to disk all scripts are
encrypted again. Surely, you will want to remember the passwords
used for your stacks, if you want to change the scripts.
The encryption doesn't slow down the execution of scripts at all.
They are decrypted when the stack opens --yet inaccessible to the
user-- and run without delay once the stack is open.
BTW, I confirm what Mark said: SSL encryption/decryption is really
amazingly fast :-)
Best regards from Paris,
Eric Chatonet.
----------------------------------------------------------------
Plugins and tutorials for Revolution: http://www.sosmartsoftware.com/
Email: [EMAIL PROTECTED]/
----------------------------------------------------------------
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
