Obfuscator (discontinued)

[Cymeria]

i get error all time from WINAPI

[Jos]

i get error all time from WINAPI

great "first" post... very informative!

Right Phodexis?

Jos

Edited February 10, 2010 by Jos

[Cymeria]

great "first" post... very informative!

Right Phodexis?

Jos

oh yes, i get much error, but i press contunie anyway, thats work correctly my compilied exes works fine.

also, yes i'm pho bu i try change my username.

My English can sometimes be insufficient

Some errors:

_WinAPI_SetLayeredWindowAttributes

___TCP_OnAccept

___TCP_Server_OnSocketEvent

_IEFormElementCheckboxSelect

_IEFormElementRadioSelect

_IEPropertyGet

_IEErrorHandlerRegister

__IEInternalErrorHandlerDeRegister

Execute

[Jos]

oh yes, i get much error, but i press contunie anyway, thats work correctly my compilied exes works fine.

also, yes i'm pho bu i try change my username.

My English can sometimes be insufficient

Some errors:

_WinAPI_SetLayeredWindowAttributes

___TCP_OnAccept

___TCP_Server_OnSocketEvent

_IEFormElementCheckboxSelect

_IEFormElementRadioSelect

_IEPropertyGet

_IEErrorHandlerRegister

__IEInternalErrorHandlerDeRegister

Execute

Whatever ... If you cannot put in any effort to be clear then please do not bother me with this BS.

...and creating a second account will get your ass banned

[MikeTranser]

Why Obfuscated make file .tbl?

[MvGulik]

whatever Edited February 7, 2011 by MvGulik

[DeanHiggins]

Great, I'm gonna try this out.

[igorm]

Hi Jos,

It seems that there are some problems with latest version of Obfuscator (v 1.0.28.7).

I'm getting the following error:

>Running Obfuscator (1.0.28.7)  from:D:\Program Files (x86)\AutoIt3\SciTE cmdline:
-###2 Obfuscation Error: Found Execute() statement which will lead to problems running your obfuscated script.
>### current Func: _WinAPI_SetLayeredWindowAttributes
D:\Program Files (x86)\AutoIt3\include\WinAPI.au3(5364,1) Warning for line:$i_transcolor = Execute('0x00' & StringMid($i_transcolor, 5, 2) & StringMid($i_transcolor, 3, 2) & StringMid($i_transcolor, 1, 2)) 

-#############################################################################################
-#### Obfuscator Found   1 Error(s)!!!!    This means your script could have problems running properly.  ####
-#############################################################################################

I'm attaching the log and my script so you can check it out, if you can.

Cheers

Online TV Lista.au3

Obfuscator.rar

[Jos]

Why do you think that Obfuscator is wrong?

Looks like there is an Execute in the included file so looks correct to me.

Obfuscator is merely telling you there is an Execute() statement and its up to you to determine if the Obfuscated result script will still work.

Jos

[OHB]

I do have a question regarding the tbl file that's created. I peered inside and found, to my dismay, that all of the strings are not encrypted. They're merely converted to hex. Are there any plans to expand this functionality to include even a basic form of encryption? If not, I would like to request that encryption of some sort is added to the to-do list.

[MvGulik]

whatever Edited February 7, 2011 by MvGulik

[igorm]

Why do you think that Obfuscator is wrong?

Looks like there is an Execute in the included file so looks correct to me.

Obfuscator is merely telling you there is an Execute() statement and its up to you to determine if the Obfuscated result script will still work.

Jos

I think it's problem with Obfuscator because this problem did not exist in maybe two or three previous versions of Obfuscator. And I get this error almost on all my scripts which is strange. Scripts seems to work fine, but it would be nice not to see that error.

Cheers

EDIT: I found the cause. I soon as I add this Include to script error will appear. I just add to empty script this Include and try to obfucsate and I get the error, so there is a problem with Obfuscator or with this include:

#Include <GuiComboBox.au3>

Edited April 20, 2010 by igorm

[Jos]

I think it's problem with Obfuscator because this problem did not exist in maybe two or three previous versions of Obfuscator. And I get this error almost on all my scripts which is strange. Scripts seems to work fine, but it would be nice not to see that error.

Cheers

EDIT: I found the cause. I soon as I add this Include to script error will appear. I just add to empty script this Include and try to obfucsate and I get the error, so there is a problem with Obfuscator or with this include:

#Include <GuiComboBox.au3>

Again: There is no problem with Obfuscator.

A change was made in one of the Include file that made it kinda incompatible with using it in Obfuscator .... that's all.

Jos

[Jos]

I do have a question regarding the tbl file that's created. I peered inside and found, to my dismay, that all of the strings are not encrypted. They're merely converted to hex. Are there any plans to expand this functionality to include even a basic form of encryption? If not, I would like to request that encryption of some sort is added to the to-do list.

Correct ... I am wondering if you understand what the whole purpose of the tbl file is and if so am wondering what it would buy you to do a proper "whatever" complex encryption on it?

Just delete those tbl files. Your Exe don't need nor uses them.

There probably forgotten(or not) debug files from the obfuscatoring process.

The file is generated during Obfuscation and FileInclude(d) during compilation.

Jos

[igorm]

Again: There is no problem with Obfuscator.

A change was made in one of the Include file that made it kinda incompatible with using it in Obfuscator .... that's all.

Jos

OK, thanks for the information. Is there a chance then, that you make it compatible?

Cheers

[Jos]

OK, thanks for the information. Is there a chance then, that you make it compatible?

Cheers

sigh... I am really trying hard to understand in which part of my answers I left room for this question?

Last try: Execute is not supported and will never be supported for the very simple fact that it cannot be fully supported. How on earth could Obfuscator be able to start figuring out what the content of a String will be?

Simple example to demonstrate what I mean:

$a=1
$v=Execute("$" & "a+1")
ConsoleWrite('$v = ' & $v & @crlf)

Does this make it any clearer?

Anyway: Using Execute will never be supported and it is up to you to figure out if the obfuscated script containing the execute statement will still function.

Jos

[OHB]

Just delete those tbl files. Your Exe don't need nor uses them.

There probably forgotten(or not) debug files from the obfuscatoring process.

True...but from what I can tell the tbl file is installed using FileInstall and extracted to the temp folder when the EXE is run. That means all of the strings are potentially quite easily available. Am I wrong about this?

[igorm]

sigh... I am really trying hard to understand in which part of my answers I left room for this question?

Last try: Execute is not supported and will never be supported for the very simple fact that it cannot be fully supported. How on earth could Obfuscator be able to start figuring out what the content of a String will be?

Simple example to demonstrate what I mean:

$a=1
$v=Execute("$" & "a+1")
ConsoleWrite('$v = ' & $v & @crlf)

Does this make it any clearer?

Anyway: Using Execute will never be supported and it is up to you to figure out if the obfuscated script containing the execute statement will still function.

Jos

OK, I partly understood you, and I appreciate your efforts to explain this to me. But, I don't understand this example. What did you want to tell me? When I run this example I got as result in console number 2. Shouldn't I get this? And, maybe I'm dumb again, but can't you make some exception for this specific problem? And what about this post here? Guy says that Obfuscator version 1.0.24.23 works fine.

Cheers

EDI: I figured the example.

Edited April 20, 2010 by igorm

[wraithdu]

Maybe I'll save Jos a few more gray hairs...

@igorm

I have no idea about the older version of Obfuscator, and practically it's irrelevant.

Obfuscator cannot and will not EVER work with the Execute() function 100% of the time. If you don't understand why by now, you need more experience with AutoIt and a full understanding of how Execute() works and how Obfuscator works. I'm not going to take the time to explain all that, and neither is Jos (or he shouldn't anyway).

Regarding your #include file and the warning... it's just that, a warning. Obfuscator will always issue that warning for include files that use the Execute() function. However if you don't actually USE the function that Obfuscator is warning about, then it makes no difference: 1) you never call the possibly problematic function, 2) Obfuscator will (by default) strip out any unused functions from your script + includes before compilation, so that code will never even be in your script.

If you ARE using the function with Execute() in it, then it's your responsibility to test your script to make sure it still works after obfuscation / compilation.

Please stop bothering the man now. This is all the information you need.

Edited April 20, 2010 by wraithdu

[MvGulik]

whatever Edited February 7, 2011 by MvGulik