Problems with AES Encryption and Corrupted Script File
Posted: Fri Nov 30, 2012 9:43 am
Hello,
Has anyone else had this problem?
We are using InstallAware NX and trying to password protect the setup executable with mixed results.
When I am password protecting the setup, the password is always accepted at the start but later the setup will fail with a script error similar to the following:
This does not happen with this setup when I do not have a password set ( AES password field is empty).
If anyone can shed some light on this it would be appreciated. I've many custom password protected builds to do for customers that are waiting.
Sheri
Has anyone else had this problem?
We are using InstallAware NX and trying to password protect the setup executable with mixed results.
When I am password protecting the setup, the password is always accepted at the start but later the setup will fail with a script error similar to the following:
- This is the script error message.
- script_err.png (5.49 KiB) Viewed 7253 times
- - If I supply a password with no special characters, it works.
- I’ve supplied passwords with no special characters longer than 32 characters – that worked.
- A password with a single dot character (.) works.
- A password with two dot characters failed.
- The original password I tried to use included $ and % characters and this failed with slightly different characters at the beginning of the "is not a valid integer" message, but always the same line in the script file.
- It also seems to happen when I uncheck the AES option but leave a password with special characters in the field (disabled).
If anyone can shed some light on this it would be appreciated. I've many custom password protected builds to do for customers that are waiting.
Sheri