Obfuscator (discontinued)

[michaelslamet]

Did you read the error message? It tells you why it won't work. Your line is longer than 2047 characters, make them shorter.

 

Thanks, BrewManNH

I did read the error message, thats why I said "the error message is clear".

After post that message, I realized maybe separate that long var into few var and then concatenate them might work.

Something like:

$sData1 = "blablbla"
$sData2 = "blablbla"
$sData3 = "blablbla"
 
Return Binary($sData1 & $sData2 & $sData3)

 

What do you think?

Also, why

#obfuscator_Ignore_Funcs=_EzMySql_Dll

 

doesn't work?

[Mat]

Also, why

#obfuscator_Ignore_Funcs=_EzMySql_Dll

doesn't work?

That flag just stops obfuscator from mangling the variable name, it doesn't change any of the other processing.

[michaelslamet]

That flag just stops obfuscator from mangling the variable name, it doesn't change any of the other processing.

 

Aha!

Thanks, Mat!

I guess I should try

#Obfuscator_On ; (default) Switch Obfuscation back on

#Obfuscator_Off ; Switch Obfuscation back off, all line following this line are not changed till its switched back on.

[wraithdu]

The error refers to individual line lengths, so you don't have to concat at the end like that. This will work too

Local $mylongvar = "blahblahblah"
$mylongvar &= "some more blah blah"
$mylongvar &= "are we done yet?"

However line continuations do not work.

[FaridAgl]

Jos, can it be changed from 2047 to 4095 to match the AutoIt's defaults/limits? That would be nice.

[Melba23]

D4RKON3,

Perhaps this will prepare you for the likely answer.

M23

[Jos]

Jos, can it be changed from 2047 to 4095 to match the AutoIt's defaults/limits? That would be nice.

As the linked page by Melba23 explains: it will never be possible to have an input record length being the same as Autoit3 as the Obfuscation process makes the record longer.

However, Obfuscator does support 4096 when using the striponly option.

Jos

[Jos]

Also, why

#obfuscator_Ignore_Funcs=_EzMySql_Dll

doesn't work?

Why should it as that only does something with the Func name , not the whole Func code?

Jos

[FaridAgl]

Thanks, that's clear now.

[michaelslamet]

Why should it as that only does something with the Func name , not the whole Func code?

Jos

 

Jos, thanks, understand

#Obfuscator_On and #Obfuscator_Off solve it

[Guest]

LOL This causes the script to look more complicated then the assembly language

Edited October 26, 2013 by Guest

[michaelslamet]

Hi Jos,

I'm not sure should I ask/report this:

I have a pretty large script which is about 4000++ lines. This script is get updated regulary. Maybe about 4 of 5 try, it will fail:

- Iteration 1 Strip Functions result: Output  14608 lines and stripped 23905 lines
- Iteration 2 Strip Variables result: Output  14608 lines and stripped 0 lines
- Iteration 3 Start the actual Obfuscation.
Can't open file C:my_foldermy_file_Obfuscated.au3
 

If this happened, the TBL file will have no content (filesize is 0), but the my_file_Obfuscated.au3 is there, just not obfuscated.

This has been happen since I use the obfuscator, that is around 1-2-3 months ago.

This is also happening to my other "large" scripts.

What I've do to make sure it sucessfull is just press F7 everytime it's failed.

Windows XP and Windows 7, AutoIT 3.8.8.1, Obfuscator 1.0.30.4

This is the directives:

#Region ;**** Directives created by AutoIt3Wrapper_GUI ****
#AutoIt3Wrapper_Run_Obfuscator=y
#AutoIt3Wrapper_Icon=my_ico.ico
#AutoIt3Wrapper_UseUpx=n
#AutoIt3Wrapper_Res_Fileversion=2.2.1
#AutoIt3Wrapper_Res_LegalCopyright=(c) me
#AutoIt3Wrapper_Res_SaveSource=n
#Obfuscator_Parameters=/sf 1
#obfuscator_Ignore_Funcs=Callback
#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****

 

Thank you

[guinness]

Download the beta version from Jos signature link. It's Obfuscator v1.0.30.13 and check the Obfuscator log to see where it's failing.

[Jos]

Hi Jos,

I'm not sure should I ask/report this:

I have a pretty large script which is about 4000++ lines. This script is get updated regulary. Maybe about 4 of 5 try, it will fail:

- Iteration 1 Strip Functions result: Output  14608 lines and stripped 23905 lines

- Iteration 2 Strip Variables result: Output  14608 lines and stripped 0 lines

- Iteration 3 Start the actual Obfuscation.

Can't open file C:my_foldermy_file_Obfuscated.au3

 

If this happened, the TBL file will have no content (filesize is 0), but the my_file_Obfuscated.au3 is there, just not obfuscated.

Could it be you have the Explorer open in the target directory and already an existing my_file_Obfuscated.au3 ?

We had similar issues with resource updating.

Jos

[michaelslamet]

Guinness and Jos:

Tried v1.0.30.13 and I can report this:

It still sometime failed, but now it has a greater sucess rate. Almost every FIRST F7 failed with SciTE output:

-#############################################################################################
- Iteration 1 Strip Functions result: Output  13404 lines and stripped 23605 lines
- Iteration 2 Strip Variables result: Output  13383 lines and stripped 0 lines
- Iteration 3 Start the actual Obfuscation.
Can't open file C:my_foldermy_file_Obfuscated.au3
 

and here is the log:

- Iteration 2 Strip Variables result: Output  13383 lines and stripped 0 lines
- Iteration 3 Start the actual Obfuscation.
53.36 ############################## Starting #######################################################################
53.36 ### Processing file:C:DOCUME~1WindowsLOCALS~1TempOBs2DB.tmp
53.36 Special Function: Functionname   Parameter:-1   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: adlibenable   Parameter: 0   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: adlibregister   Parameter: 0   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: adlibunregister   Parameter: 0   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: call   Parameter: 0   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: dllcallbackregister   Parameter: 0   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: eval   Parameter: 0   ParameterType: 1 (0=Func/1=Var)
53.36 Special Function: guictrlregisterlistviewsort   Parameter: 1   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: guictrlsetonevent   Parameter: 1   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: guiregistermsg   Parameter: 1   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: guisetonevent   Parameter: 1   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: hotkeyset   Parameter: 1   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: isdeclared   Parameter: 0   ParameterType: 1 (0=Func/1=Var)
53.36 Special Function: objevent   Parameter: 1   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: onautoitexitregister   Parameter: 0   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: onautoitexitunregister   Parameter: 0   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: opt   Parameter: 1   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: traysetonevent   Parameter: 1   ParameterType: 0 (0=Func/1=Var)
53.36 Special Function: trayitemsetonevent   Parameter: 1   ParameterType: 0 (0=Func/1=Var)
53.36 RandomStringFuncName$:A1400205E0C
53.36 ============================== Reading Source into Array ======================================================
 

The next F7 will has a much greater success chance if after press F7, I left the keyboard and mouse untouch.

So move to another application while compiling and/or continue working on the SciTE will increase the chance it's fail.

I have Windows Explorer open the target directory, but there is existing or not existing _obfuscated.au3 seems doesn't make any different.

Sometime there is an issue with resource updating too, especially when I actively move to another application after "Iteration 3" step

(after the obfuscator confirmed the encrypted _obfuscated.au3 is sucessfully created). If I left the keyboard and mouse untouch,

it's a big chance it will success.

Doesn't complain anything, who knows this report can useful

[Jos]

Have you tried without Windows Explorer open?

Try to disable your AV on the directory to see if that is somehow locking the file too long?

Jos

[legend]

If it's possible, maybe it would be a good idea, to use the following for the decryption code:

Using Inline-Assembler

In AutoIt it is possible to use Assembler if you use the FASM.au3 UDF.
This will enable you to make some parts of your script in ASM so no one will understand your script if he even does not understand ASM.
You can find a tutorial there (unfortunately only in german):
[AutoIt & Assembler] Assembler lernen und in AutoIt benutzen

[Jos]

If it's possible, maybe it would be a good idea, to use the following for the decryption code:

Using Inline-Assembler

In AutoIt it is possible to use Assembler if you use the FASM.au3 UDF.

This will enable you to make some parts of your script in ASM so no one will understand your script if he even does not understand ASM.

You can find a tutorial there (unfortunately only in german):

[AutoIt & Assembler] Assembler lernen und in AutoIt benutzen

Not sure what your suggestion is here.

Jos

[SergUlvis]

Hi everybody! 

I try to obfuscate & run a 1000-rows script.

The problem is that obfuscated code runs (F5), but after compiling & running .exe i get:

Options:

 

#AutoIt3Wrapper_Res_Compatibility=Vista,Windows7

#Obfuscator_Ignore_Funcs=ReadINI,Reconnect,Log_,Terminate

#AutoIt3Wrapper_Compression=0

#AutoIt3Wrapper_UseUpx=n

#AutoIt3Wrapper_Compile_Both=y

#AutoIt3Wrapper_UseX64=y

#AutoIt3Wrapper_Run_Tidy=y

#AutoIt3Wrapper_Run_Obfuscator=y

#Obfuscator_Parameters=/cs 1 /cn 1 /cv 1 /cf 1 /sf 1 /sv 1

 

I`ve read a lot of forum pages, know and use #Obfuscator_On/Off, #Obfuscator_Ignore_Funcs - doesn`t helped.

 

Also placed MsgBox every 2nd line from the beginning of script - no boxes, only error.

 

Can you give me some advice, please?

[mLipok]

Please send console output form Compile process.

Nobody is not a fairy, but what some have crystal balls