Clyde wrote:
I just want to provide ample protection to my Autohotkey program.
I can't answer your original question, I'm sorry, but I would suggest that it's probably a moot consideration in any case.
Because of the process a "compiled" AutoHotkey (and presumably also AutoIt) script follows when executed, the source of the script must be made available unencrypted in memory as part of the operation. At that point the source code is easily accessible.
Encrypting the .exe file with any form of security or copy protection wrapper will really only provide protection to the AutoHotkey loader itself, not the script source.
I've never needed to obtain the source from an AutoIt script that's been "compiled", but I would think it's no harder than for AutoHotkey with or without an outer encryption layer, and with or without password protection during the compile process. Others may have specific (or at least more) knowledge in that area though.
AutoHotkey is a fantastic product, but in its current form it's not really the development platform you should be looking at if source security is your main (or a major) concern.