Any work around for finding "Variable used without being declared" other than declaring all variables?

[RTFC]

  On 8/25/2017 at 2:24 PM, fopetesl said:

So the resultant exe file before enCryption is easily reverse engineered?

Expand  

Yes. Codecrypter extracts as decryption key(s) whatever you define from the script's sanctioned work environment (a user name, a VPN-bound server response, a hardware ID, your own function(s), or any combination you can think of). So anyone can make a copy of your executable or give it to others, but when that copy is run anywhere else, the environment-dependent queries you set up at the encryption stage will return different user names, hardware IDs, or whatever else you decided to use. A determined attacker might be able to find out what queries your script is sending to its work environment to construct the decryption key(s) with, but without unfettered access to the original authorised environment, the keys themselves remain completely secure (and your "decrypted" script would be utter garbage that immediately crashes). Of course, if an attacker has physical access to your machine(s), that would represent a grave security risk, but then they might as well steal your entire harddrive to obtain your data (if that's what they are after). See the CodeCrypter FAQ for additional explanation and examples.

Edited August 25, 2017 by RTFC

[fopetesl]

I immediately noticed "hardware ID" which took me four hours to resolve from BIOS number:

$DOS = Run(@ComSpec & " /c wmic bios get serialnumber >biospin.csv", "", @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD) ; BIOS code

which is easy once you know how.  However, I'll go with Codecrypter but still interested in just what 'Build' actually does in generating an 'exe' file.  Looking at an 'exe' with Hexedit there seems nothing to easily reverse engineer.  None of the raw text shows up so there's some obfuscation already?  The 'exe' has the "cannot run in DOS mode" in readable text but nothing else.

[Melba23]

fopetesl,

  Quote

 interested in just what 'Build' actually does in generating an 'exe' file

Expand  

Basically, the script is stripped of all comments and blank lines, tokenised (converted to .a3x format), and then inserted into the resource table of a precompiled interpreter stub. This means that the original script is not easily visible when looking at the exe, but is readily accessible by anyone with a little knowledge - so your little sister cannot easily see the passwords you have stored in your script, but your computer literate friend can get at them without too much problem.

M23

[RTFC]

  On 8/28/2017 at 10:18 AM, fopetesl said:

"hardware ID" which took me four hours to resolve

Expand  

Four hours?!  Maybe use this instead?

[fopetesl]

Wish I'd known that a month ago! MUCH better than 'wmic'