Obfuscator (discontinued)

[burnell]

doppelganger

look for MPRESS, it does not have decompression option and should enough for normal user.

look in this thread also:

Edited February 7, 2013 by burnell

[AHRIMANSEFID]

Not Working For Me.

Show Me Code :

RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Test\test", "ProductCode", "REG_SZ", "{83E3F4E4-CEA1-452B-9180-A40813CD111C}")
RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Test\test", "PackageFeatures", "REG_DWORD", "3")
RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Test\test", "LanguageCode", "REG_SZ", "en-us")
RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Test\test", "ProductACode", "REG_DWORD", "110")
RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Test\test", "ProductBase", "REG_DWORD", "1")
RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Test\test", "ExpirationDate", "REG_DWORD", "1451628000")
RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Test\test", "TimeStamp", "REG_DWORD", "1315976400")
RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Test\test", "LicenseCategory", "REG_DWORD", "4")
RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Test\test\01000400\Settings", "FailSafeServer"

Plz Help For Disable And encoding code and exe file.

[Chimaera]

Had a few errors lately with this

-### Obfuscation Error: Found Call() statement using unsolvable Func, which will/could lead to problems running your obfuscated script.

>### current Func: __Au3Obj_FunctionProxy

D:CodeProjectsPackAutoItObject.au3(562,1) Warning for line:Local $ret = Call($FuncName, $arg)

-###2 Obfuscation Error: Found Execute() statement which will lead to problems running your obfuscated script.

>### current Func: __Au3Obj_EnumFunctionProxy

D:CodeProjectsPackAutoItObject.au3(576,1) Warning for line:$ret = Execute($FuncName & "($oSelf, $Current)")

-###2 Obfuscation Error: Found Execute() statement which will lead to problems running your obfuscated script.

>### current Func: __Au3Obj_EnumFunctionProxy

D:CodeProjectsPackAutoItObject.au3(585,1) Warning for line:$ret = Execute($FuncName & "($oSelf, $Current)")

-### Obfuscation Error: Found DllCallbackRegister() statement using unsolvable Func, which will/could lead to problems running your obfuscated script.

>### current Func: _AutoItObject_ObjectFromDtag

D:CodeProjectsPackAutoItObject.au3(1573,1) Warning for line:DllStructSetData($tInterface, 1, DllCallbackGetPtr(DllCallbackRegister($sMethod, $sRet, $sParams)), $i + 2)

-###2 Obfuscation Error: Found Execute() statement which will lead to problems running your obfuscated script.

>### current Func: _Wlan_OnNotifHandler

D:CodeProjectsPacknativewifi.au3(4393,1) Warning for line:Return Execute($avOnNotif[$i][3] & "($avNotif)")

-### Obfuscation Error: Found ObjEvent() statement using unsolvable Func, which will/could lead to problems running your obfuscated script.

>### current Func: _CollectPatches

D:CodeProjectsPackPack.au3(778,1) Warning for line:Local $oMyError = ObjEvent("AutoIt.Error", "MyErrFunc")

-#############################################################################################

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

-#############################################################################################

+> Obfuscator v1.0.30.1 finished obfuscating 17691 lines, stripped 20794 comment lines. created:D:CodeProjects#PackPack_Obfuscated.au3

The first 5 are from the NativeWifi.au3 which also uses AutoItObject.au3 and oLinkedList.au3

And the last is from a windows update checker that i found like this

Func _CollectPatches()
    Local $colNeeded
    Local $oMyError = ObjEvent("AutoIt.Error", "MyErrFunc")
    #forceref $oMYError
    Local $objSearcher = _CreateSearcher(_CreateMSUpdateSession())
    $colNeeded = _GetNeededUpdates($objSearcher)
    $objSearcher = 0
    Return $colNeeded
EndFunc ;==>_CollectPatches

Func _CreateSearcher($objSession)
    If Not IsObj($objSession) Then Return -1
    Return $objSession.CreateUpdateSearcher
EndFunc ;==>_CreateSearcher

Func _CreateMSUpdateSession($strHost = @ComputerName)
    Local $objSession = ObjCreate("Microsoft.Update.Session", $strHost)
    If Not IsObj($objSession) Then Return 0
    Return $objSession
EndFunc ;==>_CreateMSUpdateSession

Func _GetNeededUpdates($objSearcher)
    Local $colNeeded
    SplashTextOn("Please Wait", "Checking For Updates", 220, 40, -1, -1, 18, "Tahoma", 11)
    If Not IsObj($objSearcher) Then Return -5
    $colNeeded = $objSearcher.Search("IsInstalled=0 and Type='Software'")
    SplashOff()
    Sleep(800)
    Return $colNeeded
EndFunc ;==>_GetNeededUpdates

The question is please... Is there a simple way to fix these errors or am i safe to just ignore?

Edited April 2, 2013 by Chimaera

[Jos]

.... or am i safe to just ignore?

I hope by now it is clear that the last question is a clear NO unless you do not use the code that contains the Call or Execute statements.

Jos

[FireFox]

@Jos

Why don't you suggest for this kind of errors to make sure that the function is at least clearly one time called and if it's not the case do something like this :

Local $sCall = "_MyFunc"

Call($sCall) ;_MyFunc is NOT clearly called, the function will be stripped if there is NO clear call.

If Not 1 Then _MyFunc() ;will NEVER be called but _MyFunc is NOW clearly shown as used.
Func _MyFunc()
    ConsoleWrite("toto" & @CrLf)
EndFunc

I already posted it in a topic but seems like it was ignored.

It's tricky I admit but it works fine.

Br, FireFox.

[Jos]

@Jos

Why don't you suggest for this kind of errors to make sure that the function is at least clearly one time called and if it's not the case do something like this :

Local $sCall = "_MyFunc"

Call($sCall) ;_MyFunc is NOT clearly called, the function will be stripped if there is NO clear call.

If Not 1 Then _MyFunc() ;will NEVER be called but _MyFunc is NOW clearly shown as used.
Func _MyFunc()
    ConsoleWrite("toto" & @CrLf)
EndFunc

I already posted it in a topic but seems like it was ignored.

It's tricky I admit but it works fine.

Br, FireFox.

Not sure why you suggest this?

Is this to avoid stripping out the UDF with the /sf or /so option of Obfuscator since I do not see how this resolves the use of Call or Execute in a script which Obfuscator will never be able to figure out thus Obfuscation will cripple the output script?

In that case it is easier to simply use: #Obfuscator_Ignore_Funcs=

Jos

Edited April 2, 2013 by Jos

[FireFox]

Is this to avoid stripping out the UDF with the /sf or /so option of Obfuscator

Exactly.

I do not see how this resolves the use of Call or Execute in a script which Obfuscator will never be able to figure out thus Obfuscation will cripple the output script?

It does not, but the person knows that the functions won't be stripped in spite of the errors.

Br, FireFox.

[Jos]

Exactly.

It does not, but the person knows that the functions won't be stripped in spite of the errors.

Br, FireFox.

Understand now and guess you missed my last edit.

I use "#Obfuscator_Ignore_Funcs=" for that.

Jos

[FireFox]

I use "#Obfuscator_Ignore_Funcs=" for that.

Great It's obvious when you know it.

Edit: I now understand why you did not understand the purpose of my script.

Edited April 2, 2013 by FireFox

[Jos]

Great It's obvious when you know it.

Edit: I now understand why you did not understand the purpose of my script.

Keep smiling Edited April 2, 2013 by Jos

[Chimaera]

So i guess im going to have to find ways around this then or bin the feckers altogether.

Sounds like its going to be the latter;(

btw the ignore question was because i dont know if they are big important ones or minor

Edited April 2, 2013 by Chimaera

[Jos]

So i guess im going to have to find ways around this then or bin the feckers altogether.

Sounds like its going to be the latter;(

btw the ignore question was because i dont know if they are big important ones or minor

Don't use obfuscation is the easy solution?

[Chimaera]

Im never quite sure with this whether we are supposed to use it or not? and without wishing to be rude you seem to be more on the dont lately

So im a little confused

ps if your trying to hint i dont know enough to solve the problems, i agree

Edited April 2, 2013 by Chimaera

[Jos]

Im never quite sure with this whether we are supposed to use it or not? and without wishing to be rude you seem to be more on the dont lately

So im a little confused

ps if your trying to hint i dont know enough to solve the problems, i agree

Correct, I have already decided stop the development for the Obfuscation part as there are too many people that have no idea what it does nor understands it's limitations and honestly I see it less and less serve a purpose.

It is likely I keep the stripping logic as that really cut's down the size of the stored script in the EXE and has much less limitations.

Jos

Edited April 2, 2013 by Jos

[Chimaera]

Lol no UPx, No Obfuscation... whats next

Thx for the clarification

[FireFox]

I have already decided stop the development for the Obfuscation

Does it mean that you're not going to solve the issue from my ticket? (Don't worry this one is not blocking).

It is likely I keep the stripping logic as that really cut's down the size of the stored script in the EXE and has much less limitations.

And that's the main reason why I use it

Br, FireFox.

[Jos]

Lol no UPx, No Obfuscation... whats next

Don't understand the relation between the 2, but tell me why you feel this really is a problem ?

[Jos]

Does it mean that you're not going to solve the issue from my ticket? (Don't worry this one is not blocking).

Which one is that? Ok see you created one today. Edited April 2, 2013 by Jos

[FireFox]

The one in the opened tickets list.

[Jos]

The one in the opened tickets list.

Try the latest Beta v1.0.30.4

Jos