Why no password option on the most recent compiler?
Posted 07 December 2011 - 02:20 PM
At my office they "require" that all scripts are compiled WITH a password. Even though there's no way they'll ever know if this was followed or not. Also even if someone actually bothered to take the time to decompile any of them there wouldn't be a point as it's just scripted action not something you could sell or put value on anywhere else.
Just curious. :wink:
If anyone could suggest another way to password protect or w/e I'd appreciate input.
[Moved from Ask for Help]
Posted 07 December 2011 - 08:39 PM
So you could use mpress. But because the source of ahk2exe is now available as a autohotkey script you could of course edit the Gui by adding in a password field which simply is ignored but will have your colleguages think it "helps" :twisted: :wink:
... The EXEarc library has been removed from AutoHotkeySC.bin and Ahk2Exe v1.1.01, so they won't work with older versions of AutoHotkeySC.bin or Ahk2Exe. This also means that Ahk2Exe no longer supports password protection, and supports compression and encryption only through mpress.exe, if it is present. For background information about this change, see this post.
Posted 07 December 2011 - 08:50 PM
Your office probably does not understand that scripts compiled with /NoDecompile (only supported in Basic and maybe old _L's) can be decompiled in less than 60 seconds... mpress.exe provides better protection but is also fallible.
At my office they "require" that all scripts are compiled WITH a password.
Posted 08 December 2011 - 12:57 PM
Anyone have a link to mpress? I can do a google search in the meantime. Just to check it out.