So why you don't protect it better?
I won't be bad with you or something but you want to sell this tool and for that you should protect it... Of course with an Obfuscator... I thinked about that but there was nothing! Absolutly nothing!
You could use Themida or you protect your programs with a key...
You improve your "cracking skills" by editing a plaintext script that is basically not protected?
If you really want to improve your skills, go and give SFBot a try. Good luck
Do you know that it was my first time when I crack somethig? I've thinking that there is some protection to make it harder...
Quote:
Originally Posted by _Creator_
Neither would make a real difference. Since aut2exe basically bundles an autoit launcher with the script itself, you can't do much to protect it.
I know that Decompiling AutoIt Scripts is very easy... But it would help alot against some Script Kiddys... Because if they see the obfuscated Code they get scared... Believe me
Quote:
Originally Posted by _Creator_
A .NET obfuscator for a non-.NET executable? How would that work?
I don't want to talk about the Obfuscators which he can use...
I want to tell him with this site:
Obfuscated code is source or machine code that has been made difficult to understand for humans. Programmers may deliberately obfuscate code to conceal its purpose (security through obscurity) or its logic to prevent tampering, deter reverse engineering, or as a puzzle or recreational challenge for someone reading the source code. Programs known as obfuscators transform readable code into obfuscated code using various techniques.
Obfuscating code to prevent reverse engineering is typically done to manage risks that stem from unauthorized access to source code. These risks include loss of intellectual property, ease of probing for application vulnerabilities and loss of revenue that can result when applications are reverse engineered, modified to circumvent metering or usage control and then recompiled. Obfuscating code is, therefore, also a compensating control to manage these risks. The risk is greater in computing environments such as Java [This link is external to TechNet Wiki. It will open in a new window.] and Microsoft's .NET which take advantage of just-in-time (JIT) compilation technology that allow developers to deploy an application as intermediate code rather than code which has been compiled into machine language before being deployed.
AND
Should we use an Obfuscator?
Yes, of course. you see some Obfuscators features can be used to deploy freeware applications.
1 - Resources compression: Compresses managed resources to reduce the size of the assembly.
2 - Dependencies merging: Takes all the DLLs and merges dependencies into the main assembly, so you don't have to load lots of DLL files, and so that they can also be obfuscated.
3 - Dependencies compression and embedding: Compresses and embeds your dependencies into your main assembly, simplifying the deployment of your software and reducing the size of your program.
4 - Unused Code Removal: remove unused codes make .NET assembly smaller.
I will delete it of course...
But at first I want that he understand how to protect his Programs before he want to sell them or before he is going to release them
[Release] BotStarter (starts SeaBot and SeaCrusher) 12/05/2012 - Seafight - 70 Replies Read this
Guten Morgen liebe Community,
Nach einigen langen Nächten und intensiver Arbeit kann ich euch heute den SeaBotStarter präsentieren.
Er verwaltet bis zu 15 Seabots und lässt euch in Ruhe schlafen, denn ab sofort werdet ihr morgens aufwachen und die Bots tun ihre Arbeit. ;)
Features:
- startet bis zu 15 Seabots (NEU: Jetzt auch SeaCrusher!)