Protecting a bot - Whats best?

DtehD

Newbie
Joined
Dec 30, 2011
Messages
23
Reaction score
1
Alright, i want to start selling a bot. But i've had a look around and the problem is that a ton of bots are getting cracked.
What is the best way to protect my bot, also needs license system in it.
Of course, i've been looking around myself. All i could find were some old threads from 2010.
What would be the best way to stop the crackers or at least, make it so that the really rubbish crackers will not be able to crack it?
Anyone got suggestions for obfuscators/licensing software etc to use?
Preferably free, but i can pay some money too.
 
You could try this .Net obfuscator:
.NET Obfuscator Skater Light
Its free but i never try it myself.
There is a lot of tools for this but not so much which are free.

For license, search in MSDN for LicenseManager Class or you can implement your own authentification process logic.
 
To tell the truth, I've been programming in .net for a while. I decided one day to try to crack a bot, and I even cracked an obfuscated
One with ease(changed 1 line of code with reflector). It's literally almost impossible to keep it from being cracked, I'm willing to test if you want against your protections
 
To tell the truth, I've been programming in .net for a while. I decided one day to try to crack a bot, and I even cracked an obfuscated
One with ease(changed 1 line of code with reflector). It's literally almost impossible to keep it from being cracked, I'm willing to test if you want against your protections

You are correct but can still work for sunday's crackers.
 
I would say your best bet is multiple Auth procedures that are all decoys and only one will be the real one, making it harder on the cracker
 
Have you tried
Software passport? Used to be called Armadillo.
Code:
http://www.siliconrealms.com/
 
You can slow the work of crackers, but not protect 100%, but you know that.

You should not build your bot in .NET/C# (too easy to decompile), but prefer Delphi or C++.
Also prefer to build your own protection, do not use all-in-one protection system (like WinLicence).
Another simple thing will be to compress the EXE with PECompact or another reputed packer (not UPX).

Beny
 
.NET reactor for obfuscation.

Ultimately you can't protect against reverse engineering, but you should aim to make it very difficult.
 
If the bots any good then while sell it when you can use it. Your opening yourself up to litigation as we saw with TA and other twitter bot makers.
 
hey kokoloko75 , Chris22 and oxonbeef.... nobody can crack scrapebox. what do you think about that?
 
hey kokoloko75 , Chris22 and oxonbeef.... nobody can crack scrapebox. what do you think about that?

Of course ScrapeBox can be cracked, but it would be hard because it check licence online at start.
ScrapeBox is cheap and built by BHW members, so nobody will be so stupid to waste his time to crack it.
Support this small team.

The question can be asked for XRumer...

Beny
 
As a developer that has sold over 100,000 copies of automated software...

Don't dwell on cracks. Don't worry about it, just worry about the money. Everything can and will be cracked. You should view it as a badge of honor that your prog was so needed that crackers paid attention to it
 
As a developer that has sold over 100,000 copies of automated software...

Don't dwell on cracks. Don't worry about it, just worry about the money. Everything can and will be cracked. You should view it as a badge of honor that your prog was so needed that crackers paid attention to it

I agree.

A good example is Adobe. They don't care about cracking...
Their customers are companies with bulk licences orders.

Beny
 
I'm setting my licensing system up in such a way that if my software was cracked, I'd know who was responsible for it.

I think this is time better spent than spending time trying to prevent cracking.
 
Last edited:
Back
Top