"Encrypted" script?

We are using a well known installer system to create our installations. Unfortunately, we found out that, when our installer is launched, the script is written into the Windows \temp folder. The problem is that the script holds all the information of a setup project. It can be viewed with a regular text editor, as it is not encrypted in any way. It's just a couple of minutes of work to find the password!!!!!

Does SB5 have the same problem? Using SB4 is not an option because we need scripting capability.

Thanks in advance.

SB5 compiles native 32-bit setup executables and the script is not accessible.