@link,
Ever considered making your tool compatible with AutoHotkey Basic also?
Vlad
Ever considered making your tool compatible with AutoHotkey Basic also?
Vlad
AutoIt3 Decompiler
11/01/2011 21:25
SuiBom#46
11/08/2011 16:08
Cholik#47
Mein Gott mach aus einer Mücke doch keinen Elefanten... natürlich ist es nur Verletzung der AGB, ist schon klar, dass man damit nicht gegen geltendes Deutsches Recht verstößt, aber dennoch gegen die AGB, was viele wohl für sehr sehr schlimm halten.Quote:
Bullshit. Wer gegen irgendwelche AGBs verstößt, verstößt noch lange nicht gegen geltendes Deutsches Recht. In Deutschland ist Reverse Engineering [Only registered and activated users can see links. Click Here To Register...].
Btw. du kannst auch die Edit-Funktion nutzen, du musst nicht extra deinen Post löschen und einen neuen darunter setzen, wenn du etwas veränderst. :P
11/08/2011 21:58
NUKER_PUMA#48
Direkt mal runtergeladen (Y)
Danke :)
Kriegst'n thanks^^
Danke :)
Kriegst'n thanks^^
11/22/2011 12:22
scbiz#49
Das weiß ich selbst, sieht aber schöner aus, zumindest für die Nicht(zumxtenmal)moderatoren unter uns.Quote:
12/04/2011 21:44
~.ScoiL#50
Habe meinen Crypter heute fertig bekommen, als ich es mit dem Decompiler ausprobiert habe war er schon wieder detected. :facepalm:
Ich probier es so lang bis der Decompiler versagt. :D
Ich probier es so lang bis der Decompiler versagt. :D
12/17/2011 14:34
link#51
Hab's erneut geupdated. Die halbfertige Version hab ich schon vor Wochen angefangen, aber nie fertig geschrieben. Eigentlich ist v5 immer noch nicht fertig, aber da ich zZ irgendwie wenig Bock habe, daran weiter zu schreiben, hab ich jetzt mehr oder weniger einfach das halbfertige Programm gepostet. Groesstenteils ist es nur hingeschmiert, damit ueberhaupt irgendwas drinnen ist. Wird also wahrscheinlich haeufig abstuerzen/nicht funktionieren.
@SuiBom:
I actually just wrote this tool to annoy e*pvp's users who use AutoIt.
And since there are not many ppl on this forum using AutoHotkey I didn't make any efforts to do so yet.
@SuiBom:
I actually just wrote this tool to annoy e*pvp's users who use AutoIt.
And since there are not many ppl on this forum using AutoHotkey I didn't make any efforts to do so yet.
12/19/2011 20:55
SuiBom#52
Fair decision.Quote:
I actually just wrote this tool to annoy e*pvp's users who use AutoIt.
And since there are not many ppl on this forum using AutoHotkey I didn't make any efforts to do so yet.
Nice job on the update.
12/25/2011 05:28
DuguWudi#53
Autoit just got updated to new version, waiting for your next release patiently.
BTW nice job. I use both autoit and autohotkey previously, but now just keep it as a reference in case I need it. The only method to protect from decompilation so far is using the easiest method, that is by not telling anyone you wrote the app using autohotkey or autoit and wrap/protect it. That way, anyone that simply download a decompiler tool wont be able to go pass the first defense(for normal user). Too bad, alot of people like to spread about what tool they use to write the app(I happened to be one of them previously until I learn my lesson by keeping my mouth shut).
BTW nice job. I use both autoit and autohotkey previously, but now just keep it as a reference in case I need it. The only method to protect from decompilation so far is using the easiest method, that is by not telling anyone you wrote the app using autohotkey or autoit and wrap/protect it. That way, anyone that simply download a decompiler tool wont be able to go pass the first defense(for normal user). Too bad, alot of people like to spread about what tool they use to write the app(I happened to be one of them previously until I learn my lesson by keeping my mouth shut).
12/27/2011 16:47
ouka#54
Krasses ding, fettes lob, das tool ist übermächtig und sollte verboten sein ^^
12/28/2011 03:13
link#55
hehe, hoert man gern (denke ich)
@DuguWudi:
it should still work with v3.3.8.0.
btw. you don't need to know which embedder or compiler was used. Often you can tell by the executable's characteristics or by the resources and plaintext it contains.
@DuguWudi:
it should still work with v3.3.8.0.
btw. you don't need to know which embedder or compiler was used. Often you can tell by the executable's characteristics or by the resources and plaintext it contains.
01/25/2012 20:24
necross1234#56
Maybe I'm just dumb, but where's the download link for the decompiler?
01/25/2012 20:36
jacky919#57
It seems that he removed the downloadlink, but he wrote he is only reworking the code.
01/29/2012 05:30
DuguWudi#58
If you mean, manifest and version info for the wrapper, normally I would remove it if its possible.;) Unfortunately removing those 2 thing from the actual autoit exe file isnt possible.:( Thats why I normally wrap the actual autoit file with a wrapper.:DQuote:
@DuguWudi:
it should still work with v3.3.8.0.
btw. you don't need to know which embedder or compiler was used. Often you can tell by the executable's characteristics or by the resources and plaintext it contains.
02/03/2012 07:17
johnapolo#59
kk
02/03/2012 17:09
link#60
With characteristics I actually meant things like which API functions are imported, is a JMP-table being used, which calling convention is used, how does the pro- and epilogue look like, how does the DOS stub look like, etc.
Most of them can vary depending on the compiler options, though, they can give you hints on which compiler or embedder is the executable's origin.
Most of them can vary depending on the compiler options, though, they can give you hints on which compiler or embedder is the executable's origin.