Decompiling

Post a reply

Confirmation code
Enter the code exactly as it appears. All letters are case insensitive.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :| :mrgreen: :geek: :ugeek: :arrow: :angel: :clap: :crazy: :eh: :lolno: :problem: :shh: :shifty: :sick: :silent: :think: :thumbup: :thumbdown: :salute: :wave: :wtf: :yawn: :facepalm: :bravo: :dance: :beard: :morebeard: :xmas: :HeHe: :trollface: :cookie: :rainbow: :monkeysee: :monkeysay: :happybday: :headwall: :offtopic: :superhappy: :terms: :beer:
View more smilies

BBCode is ON
[img] is OFF
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Decompiling

Re: Decompiling

by SOTE » 08 Oct 2018, 22:16

HotKeyIt wrote:
lolkaru wrote:How to set password? With the default password, program does not start, error like this:
https://image.prntscr.com/image/Ly4_zKz ... pE1sgg.png

If I did not set a password, and only used compression, will the program be hacked easily? Thx.
https://github.com/HotKeyIt/ahkdll/issues/15
Image
kapastratos wrote: Hello,

I did it but I got an error (see picture).

Any help on that please?
This error appears to come from not renaming AutoHotkey.exe (from ahkdll-v1-release-master\Win32w\) to Ahk2Exe.exe. AutoHotkey.exe must be renamed to Ahk2Exe.exe
The wording can possibly cause confusion, because it's not just copying the file over, but renaming the file too.

Maybe AutoHotkey.exe should have been renamed as Ahk2Exe.exe and put in the ahkdll-v1-release-master\Compiler\ directory by default. So when downloaded, it can be used immediately. Another area of confusion is downloading from the wrong directory. The person might have linked or downloaded from the Ahk2Exe directory, instead of the ahkdll-v1-release directory. That directory has a file called, Ahk2Exe.ahk. And this could result in confusion and getting errors. With this link, you can see all of the different HotKeyIt directories. https://github.com/HotKeyIt From there, a person can see the correct directory to choose, ahkdll-v1-release. This includes helping to prevent confusion about the ahkdll-v2-release directory VS the ahkdll-v1-release directory.

Image
This error comes from not using the default password of AutoHotkey. How or the best way to change the password, other than using the default, is still a bit fuzzy and difficult. It would be great if the process was more automated and convenient. Perhaps something along the lines of what Feiyue has done.
https://autohotkey.com/boards/viewtopic ... 28&t=42494
That is have the Ahk2Exe script to Exe converter encrypt the script with whatever password the user chooses, but this is carried out by an additional function that does not require the source code to be recompiled. This possible additional encrypt and decrypt function could be added by the Ahk2Exe script or "pre-built" into the source code. Maybe allowing the user to encrypt the script with whatever password they choose.

Re: Decompiling

by HotKeyIt » 26 Jun 2018, 16:08

lolkaru wrote:How to set password? With the default password, program does not start, error like this:
https://image.prntscr.com/image/Ly4_zKz ... pE1sgg.png

If I did not set a password, and only used compression, will the program be hacked easily? Thx.
https://github.com/HotKeyIt/ahkdll/issues/15

Re: Decompiling

by coffee » 26 Jun 2018, 02:02

AHKtreasureland wrote:This is great, best things In life are free indeed. I really appreciate this.

I was wondering if the lib folder could be packed together when AHK_H gets recompiled.
Not talking about the moment of compiling, but prior to that i.e. the time that AHK_H gets recompiled with Visual Studio.
Not sure if I got that right but Autohotkey_h can use libraries packed as resources. Some functions in autohotkey_h are actually .ahk library files added as resources in the exe after c++ compile. Look at the "CleanUpAndPack.ahk" script included in the autohotkey_h source.
e.g: https://github.com/HotKeyIt/ahkdll/blob ... ck.ahk#L37

Re: Decompiling

by AHKtreasureland » 26 Jun 2018, 00:46

This is great, best things In life are free indeed. I really appreciate this.

I was wondering if the lib folder could be packed together when AHK_H gets recompiled.
Not talking about the moment of compiling, but prior to that i.e. the time that AHK_H gets recompiled with Visual Studio.
HotKeyIt wrote:1. If you make a proper or even dynamic password it will be very difficult, there is always a way to decompile :)
2. Yes you could do but I an not sure what you can do. (obfuscation!?)
Also if you could throw yet a few more free stuff regarding methods to create proper/dynamic password at the time AutoHotkey_H gets recompiled with Visual Studio. Thank you, Mr. HotKeyIt.

Re: Decompiling

by lolkaru » 26 Aug 2017, 20:35

How to set password? With the default password, program does not start, error like this:
https://image.prntscr.com/image/Ly4_zKz ... pE1sgg.png

If I did not set a password, and only used compression, will the program be hacked easily? Thx.

Re: Decompiling

by HotKeyIt » 26 Jul 2017, 13:37

Yes, before you change password here, you need to recompile the source with that password as mentioned above!

Re: Decompiling

by tm6464 » 26 Jul 2017, 03:51

sir, if i change pw here
Image
my progamm not start
Image

Re: Decompiling

by HotKeyIt » 21 Jul 2017, 07:43

1. If you make a proper or even dynamic password it will be very difficult, there is always a way to decompile :)
2. Yes you could do but I an not sure what you can do. (obfuscation!?)

Re: Decompiling

by tm6464 » 21 Jul 2017, 05:14

thx great work

is there any way to decompile full code now?

is there anything i can do to make the code even more secure?

thx

Re: Decompiling

by HotKeyIt » 29 Jan 2017, 20:03

Yes using ;@Ahk2Exe-SetName Awesome, see Upcoming Ahk2Exe changes.

Re: Decompiling

by fenchai » 29 Jan 2017, 18:41

HotKeyIt wrote:HotKeyIt
After Compiling, the name of my exes only say "AutoHotkey_H Unicode base 64" Is there a way to change it to script name?
edit:nvm I can use Resource hacker to change the Process Name

Re: Decompiling

by fenchai » 22 Jan 2017, 20:41

HotKeyIt wrote:If you want to protect your script properly, you need to change the password and recompile the exe, otherwise it is possible to extract resources from exe and decode it the same way how Ahk2Exe encodes them using the default password.
I see... But right now, since RCData was encrypted it at least adds a rough layer for common to techy people like myself from looking for other ways to hack the compiled.exe
But I know that if someone really wants to they can find someone to hack it, but who is going to do that. :D not even worth it at this point. IMHO. Thanks for your incredible creation :)

Re: Decompiling

by HotKeyIt » 22 Jan 2017, 04:26

If you want to protect your script properly, you need to change the password and recompile the exe, otherwise it is possible to extract resources from exe and decode it the same way how Ahk2Exe encodes them using the default password.

Re: Decompiling

by fenchai » 22 Jan 2017, 00:19

HotKeyIt wrote:What do you mean by syntaxes, there is v1 and v2 compiler included in the downolads.
Sorry about that, I forgot about v2 alpha. About the password, does changing the password improve the security of the compiled .exe in any way or is it even worth it?

Re: Decompiling

by masheen » 21 Jan 2017, 17:49

samardac wrote:How to prevent compiled AHK .exe from decompiling?
download 7zip -> setup it -> right click on ahk.exe -> unzip

Re: Decompiling

by HotKeyIt » 21 Jan 2017, 15:57

The Password in downloaded exes, bins and dlls is AutoHotkey. That is also the content of password control.
If you like to change the password you have to recompile AutoHotkey.exe/bin/dll using Visual Studio and source code on github, then you have to enter the password you used into that control.

In AHK_H you can compile exe and dll as well. The correct bin file depends on whether your script requires ANSI(Win32a) or is it UNICODE (Win32w+x64w) compatible.
What do you mean by syntaxes, there is v1 and v2 compiler included in the downolads.

Re: Decompiling

by fenchai » 21 Jan 2017, 13:48

HotKeyIt wrote:I have improved anti-debugging features in AutoHotkey_H so protection should be even better now ;)
(Sorry for the pointless quote, I do not know how to summon you with reply yet :/)

Hi!

I used your compiler and it worked on my AHK v1 script :) I have a few questions about the compiler.

* What does the password used in executable mean? what is it for?
* How do I know the correct .bin file besides trying each and every one of them?
* Why is the compiler using syntaxes from v2?

Re: Decompiling

by HotKeyIt » 21 Jan 2017, 05:44

I have improved anti-debugging features in AutoHotkey_H so protection should be even better now ;)

Re: Decompiling

by guest3456 » 26 Dec 2016, 13:28

samardac wrote:HotKeyIt,
Why I get this? All paths are correct.
Image
don't use the default .bin file. you have to specifically choose one of the other AHK_H .bin files from the list

Re: Decompiling

by Tomer » 21 Sep 2016, 06:36

guest3456 wrote:
Tomer wrote: 3. Copy ahkdll-v1-release-master\Win32w\AutoHotkey.exe to ahkdll-v1-release-master\Compiler\Ahk2Exe.exe - done
4. Double click Ahk2Exe.exe - I cant find this file in the zip ?

help ?
the file isn't in the zip. you claimed to do #3 but obviously you didn't.
well you right!,

I renamed the file: "\ahkdll-v1-release-master\ahkdll-v1-release-master\Win32w\AutoHotkey.exe" to Ahk2Exe.exe.
now its working good :)

Top