AutoCamo - 98.18b

[Mobius]

fileinstall dont work

I might reactivate this one day to see if this is true.

[mesale0077]

hi

my autoit version, :autoit 3,3,95

after compiler

$Combo1 = GUICtrlCreateCombo(". dont work

expandcollapse popup

#include <ButtonConstants.au3>
#include <EditConstants.au3>
#include <GUIConstantsEx.au3>
#include <StaticConstants.au3>
#include <WindowsConstants.au3>
#include <file.au3>
#include <Word.au3>

$Form1 = GUICreate("[#] Change Find [#]", 463, 373, -1, -1)
$Button1 = GUICtrlCreateButton("Select Folder", 288, 32, 145, 33, $WS_GROUP)
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Edit1 = GUICtrlCreateEdit("", 24, 104, 409, 73)
GUICtrlSetData(-1, "Enter the word to change")
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Input1 = GUICtrlCreateInput("", 32, 40, 241, 24)
GUICtrlSetFont(-1, 10, 800, 0, "MS Sans Serif")
$Label2 = GUICtrlCreateLabel("Change Find", 32, 8, 94, 24)
GUICtrlSetFont(-1, 12, 800, 0, "MS Sans Serif")
$Button2 = GUICtrlCreateButton("Change ", 104, 312, 219, 49, $WS_GROUP)
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Label3 = GUICtrlCreateLabel("Word Find :", 24, 72, 116, 28)
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Edit2 = GUICtrlCreateEdit("", 24, 224, 409, 73)
GUICtrlSetData(-1, "Please enter a new")
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Label4 = GUICtrlCreateLabel("Word Change:", 24, 192, 156, 28)
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Label5 = GUICtrlCreateLabel("Extension :", 264, 72, 73, 28)
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Combo1 = GUICtrlCreateCombo(".html", 360, 72, 65, 25)
GUICtrlSetData(-1, ".htm|.ini|.txt|.log|.doc|.bat|.vbs|.hta|.au3|.reg|.js|", ".html")
GUISetState(@SW_SHOW)
#EndRegion ### END Koda GUI section ###
While 1
$nMsg = GUIGetMsg()
Switch $nMsg
  Case $GUI_EVENT_CLOSE
 
   Exit
EndSwitch
WEnd

and

I get this error in the following code.

error:

"canvas does not allow drawing"

expandcollapse popup

#include <ButtonConstants.au3>
#include <EditConstants.au3>
#include <GUIConstantsEx.au3>
#include <StaticConstants.au3>
#include <WindowsConstants.au3>
#include <file.au3>
#include <Word.au3>
install()
func install()
FileInstall("D:aghhh.skin",@TempDir & "ghhh.skin")
FileInstall("D:askinengine.dll",@TempDir & "skinengine.dll")
endfunc
#Region ### START Koda GUI section ### Form=
$dll = DllOpen(@TempDir & "skinengine.dll")
DllCall($dll, "int", "InitSkinEngine")
DllCall($dll, "int", "ProvideLicenseKey", "str", "demoonly")
DllCall($dll, "int", "LoadSkinFromFile", "str", @TempDir & "ghhh.skin")
DllCall($dll, "int", "ApplySkinEngine")
$Form1 = GUICreate("[#] Change Find [#]", 463, 373, -1, -1)
$Button1 = GUICtrlCreateButton("Select Folder", 288, 32, 145, 33, $WS_GROUP)
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Edit1 = GUICtrlCreateEdit("", 24, 104, 409, 73)
GUICtrlSetData(-1, "Enter the word to change")
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Input1 = GUICtrlCreateInput("", 32, 40, 241, 24)
GUICtrlSetFont(-1, 10, 800, 0, "MS Sans Serif")
$Label2 = GUICtrlCreateLabel("Change Find", 32, 8, 94, 24)
GUICtrlSetFont(-1, 12, 800, 0, "MS Sans Serif")
$Button2 = GUICtrlCreateButton("Change ", 104, 312, 219, 49, $WS_GROUP)
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Label3 = GUICtrlCreateLabel("Word Find :", 24, 72, 116, 28)
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Edit2 = GUICtrlCreateEdit("", 24, 224, 409, 73)
GUICtrlSetData(-1, "Please enter a new")
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Label4 = GUICtrlCreateLabel("Word Change:", 24, 192, 156, 28)
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Label5 = GUICtrlCreateLabel("Extension :", 264, 72, 73, 28)
GUICtrlSetFont(-1, 14, 800, 0, "MS Sans Serif")
$Combo1 = GUICtrlCreateCombo(".html", 360, 72, 65, 25)
GUICtrlSetData(-1, ".htm|.ini|.txt|.log|.doc|.bat|.vbs|.hta|.au3|.reg|.js|", ".html")
GUISetState(@SW_SHOW)
#EndRegion ### END Koda GUI section ###
While 1
$nMsg = GUIGetMsg()
Switch $nMsg
  Case $GUI_EVENT_CLOSE
 
 
   GUIDelete()
   DllCall($dll, "int", "FreeSkinEngine")
DllClose($dll)
  ; filedelete(@Windowsdir & "skinengine.dll")
  ;filedelete(@Windowsdir & "tiger.skin")
   Exit
EndSwitch
WEnd

nice program

[wraithdu]

AutoIt 3395 is 100% alpha (and not even public). The interpreter, compiler, everything is changed. I wouldn't expect an app like this to work with it, and I'm not sure it's worth the author's time to try to make it compatible until we at least get to a public beta stage.

[AdmiralAlkex]

You can find 3.3.9.5 in the usual (beta) places, and the download page ("download beta" button and make sure to take the right version).

[Mobius]

Thanks Admiral

here, have a dilithium crystal *

Vlad

[yahaosoft]

great works!

thanks for sharing it for all people.

[Mobius]

A3C 76.10 update.

See first thread for download

Vlad

Edited June 14, 2013 by Mobius

[michaelslamet]

Hi,

I'm sorry for asking this stupid question: obfuscating is to make it harder to decompile, or not related to decompile, but when users finally can decompile our exe file, he will not understand the source code?

Also if I read post from william, this script can strip "autoit" text on the exe file? I'm asking this because i'm sick Avast give a false alarm almost everytime!

So the best thing I can do is disable Avast of computers that running autoit script.

Can I use this script to bypass the Avast false alarm?

Thanks!

[FireFox]

after compiler

$Combo1 = GUICtrlCreateCombo(". dont work

See >this reply... (ok I'm a little bit late; better late than never)

Edited June 13, 2013 by FireFox

[Mobius]

My bad, you can blame my tardiness on "Brutal DOOM" for the "Zandronum" engine. Best pain killer ever!

Hi,I'm sorry for asking this stupid question: obfuscating is to make it harder to decompile, or not related to decompile, but when users finally can decompile our exe file, he will not understand the source code?

Thats not a stupid question at all dude, the obfuscation a3c provides is not at the source level, merely at the a3x data level.

This a3x obfuscation is focused against one particular static (ancient) method of AutoIt executable decompilation.

I highly recommend that you obfuscate your sourcecode as well to provide different layers of confusion.

Also if I read post from william, this script can strip "autoit" text on the exe file? I'm asking this because i'm sick Avast give a false alarm almost everytime!So the best thing I can do is disable Avast of computers that running autoit script.Can I use this script to bypass the Avast false alarm? Thanks!

Yes it can modify the output exe entirely to your design, with this in mind and some time and knowledge from its user, it could also assist with Antivirus confusion.

However it will take more (usually alot more) than simply stripping/changing/mangling the 30 or so intances of the unicode string "AutoIt" in the interpreter to achieve this .

It is a sign of morbidly flawed times when your average user is willing to go as dark on they're work as malware authors, just so they can run/distribute it.

In all honesty michaelslamet, if your AV is freaking out about a typical AutoIt exe, it is eventually going to have a kitten over a heavily modified one.

Vlad

[Mobius]

Users of AutoCamo 76.10 (forget 62.9) should be aware that

the new beta AutoIt updates 3.3.9.6 + Use build mechanisms

that are subtly different to previous builds.

These changes make it difficult but not impossible to build

a standalone exe with A3C in the traditional way.

3.3.9.6 beta camoed exe example:

A3C could be made aware of this change in a future update as

the use of the resource table to store the source is nice.

I wouldn't recommend attempting to build these new range of

beta releases with A3C until that happens, unless you like

errors or hardcore configuration of A3C and DRXL.

Vlad

[willichan]

Hi Vlad,

I have not been using A3C for a couple of years, but thanks to an old client's "genius" son   I am looking into it again.  Unfortunately, I have not been able to get the latest version to work.  When constructing the simple.au3 script from the Examples folder, I get the following in the log:

A2E: C:\Program Files (x86)\AutoIt3\Aut2Exe\Aut2exe.exe

BIN: C:\Program Files (x86)\AutoIt3\Aut2Exe\AutoItSC.bin

DIR: F:DownloadsAutoITAutoIt3CamoAutoCamoA3CExamples

IN F:DownloadsAutoITAutoIt3CamoAutoCamoA3CExamplessimple.au3

OUT F:DownloadsAutoITAutoIt3CamoAutoCamoA3CExamplessimple.exe

IRI 99

DCE 0

TMP 0

DCA 0

DBG 1

SUB WIN

KOR 1

A2E C:\Program Files (x86)\AutoIt3\Aut2Exe\Aut2exe.exe

BIN C:\Program Files (x86)\AutoIt3\Aut2Exe\AutoItSC.bin

ACE 0

PBC 0

VRL 2057

CMP 2

DNB 0

AII 0

X64 0

Compiler unpack - Error 1

Can't create temporary compiler! C:\Program Files (x86)\AutoIt3\Aut2Exe\A2ECamo.exe

 

Reading the introduction from the help, I found where you state that A3C is for 32-bit XP, and will not work well for modern windows.  Although compiling 32-bit exe files, I am running 64-bit Win7.  Is this actually unsupported, or just a case of a doc file that hasn't been updated yet?  If the latter, any hints on what I am doing wrong?  Is there a setting that can put the temporary compiler in a different location?

Thanks for the help.

[FireFox]

Run A3C with administrator privileges and see if it works.

Edited October 27, 2013 by FireFox

[willichan]

Running as administrator works.  Thank you FireFox.

Is there a reason for putting the temporary compiler in the programs folder instead of a temp folder or the ProgramData folder?

[Mobius]

Hi willichan,

And also thanks to FireFox for holding the fort

The reason the temporary compiler is created in the same folder as the original has to do with includes.

If your work does not require distributed includes, the compiler and interpreter can be put anywhere.

And no it isn't an unfinished document, those using currently released versions of A3C with post XP systems such as vista or W7 can expect problems across the board.

It is a miracle it still gets the attention it does quite frankly, I'd love to trash it since AutoIt has, and only needs one build wrapper.

Vlad

Edited October 29, 2013 by Mobius

[Ontosy]

AutoItSC.bin is missing in v3.3.10.0. How to do?

with old version i obtain a error: "Application integrity can't be verified".

Edited December 23, 2013 by Ontosy

[Mobius]

Hi Ontosy & everyone else,

AutoCamo has been updated which should fix the problem you were having using it with the latest stable build of AutoIt

See first thread for download and second for basic update information

Vlad

[MyDream]

Thank you, might try test it out as soon as possible when I'm free.

[Ontosy]

Thank you, it work fine in a computer.
In other i have a "Unable to open the script file" error and in the log i see a
"Create failed: C:Documents and SettingsmyuserLocal SettingsApplication DataAutoIt v3Aut2ExeA3C_HVYWZCEQHWNAM.a3x"
and
Read error: C:Documents and SettingsmyuserLocal SettingsApplication DataAutoIt v3Aut2ExeA3C_HVYWZCEQHWNAM.bin
Fuzz Interpreter failed
do it is a antivirus problem (i not can to stop it)?

no problem with previous version.
How to fix?

Edited January 2, 2014 by Ontosy

[Mobius]

Pre update test 81.12

A quick fix update which may or may not help but certainly caused some author facepalms

It is safe to extract this over the 81.11 install directory if you want to.

81.12 fixes

Forgot to bundle the keyboard shortcut rtf help reference.

In the console sub window the option to clear the edit boxes from the elements menu was broken.

In the patches sub window the add element menu items also populated the description edit box when selected.

A static string where api should have been used to retrieve the temporary directory location in windows xp. Also should this windows returned path be invalid, the user temp folder will be used.

Certain elements of the build were not using the temporary directory, which may or may not trigger security tools, Now nothing should be created / manipulated outside of this folder (unless the user instructs) until the creation of the final executable. The temporary folder is identical to the one used by Aut2Exe so it is recommended you instruct your Security tool to ignore this folder.

Cleaned up the info text in the distributed examples.

Additional notes

Users that have excluded the temporary directory that Aut2Exe uses In thier AV options but are still getting problems when AutoCamo attempts to write the temporary compiler to the folder of the original compiler, can run AC.exe with the ~c2t commandline switch before building to force it to create and execute the compiler from the temporary directory.

Users that do this must also have run a pre processing tool like obfuscator to gather all includes into a single file, otherwise the temporary compiler will not be able to find any includes because it does not reside in the original compilers folder.

Vlad