In the case of KiXcrypt you define it when you create the crypted version of the script. The command line is encrypted within the executable, and is used to start the interpreter - it is never actually written out anywhere.
A full example of a command line to encrypt a script with a password passed via the command line is:
code:
kixcrypt logon.kix kix32.exe %s $Password=mypassword
This creates an executable which when run will extract and execute the logon.kix script, passing the password "mypassword" in as the variable $Password.
You can do a similar thing with batch files. To pass a password to an encrypted batch file:
code:
kixcrypt -k logon.bat %s mypassword
Now, the password "mypassword" is available in the batch file as positional parameter "%1".
The "-k" switch stops KiXcrypt adding the KiXtart commands to delete the file, which if course would cause an error in a batch file.
The drawback is that if you change the password you need to recreate the encrypted script.
