Protecting your Software

  1. Demo
    Ok, in my opinion, this one of the safest methods.
    What do I mean with a demo? Well, this is your program, with a few functions left out.
    For example, you can have all functions, but you cannot save your work.
    This is a good way, as your users are able to get to know your program, and if they like they need to buy it, as they cannot save their work.
    But of course not ALL programs have a save function. There is always something you can disable, but don’t disable too much, as you need to show the program functioning.

Now the great advantage is that this is almost uncrackable (through reverse engineering, you may try to add the functions, but in VB this is pretty hard,and if you just LET OUT the code for that function, it is pretty close to impossible), the disadvantage is if one person buys it, and places it on the internet, you have no more security.
But you’ll have to trust your users (or place a secret code in every copy you send which is attached to the user, so you can sue that user for pirating your software).

  1. Trialware
    This is almost the same as a demo, BUT all the functions are there. The difference is that your program ‘expires’ after a while (most of the time 30 days, but this is at your wish)
    Now a great ‘problem’ is that most of the time, this is a pretty easy to crack protection.
    Well, it all depends on the way you are making this.
    A fact is: you need a date to check against (well… not totally true, check the last part of Trialware)
    As you need to check that date, you will need to store it somewhere:
  • in a file called “trialdate.txt”
  • in the registry under your programs keys “LastDate” = …
    NO! That is very stupid, as just changing this, is very easy, and your security is gone.
    Better ways to do this:
  • in a file called “QLSKE.DJ.sys” under the Windows\System\Drivers, or something like that
  • in the registry under key not that easy to recognise (Windows\CurrentVersion) and call it something like “WindowsRegistrationCode”, you get the idea
    Another thing you should do, is encrypt this date (easy/hard), as this makes it ten times harder to crack it
    Well, the advantage of this is your users can taste the FULL flavor of your program, but the disadvantage is that these protections tend to crack easily. (there are programs around that see what files or registry keys are accessed)

Ok, trialware does not HAVE to be with a date, you can do it with a counter too, 30 uses, then it closes.
IMHO, I think you need a few things to make this even MORE secure! Here is my idea:

Now what to do when expiration date is reached ?
Well, you could just tell your user: “Expiration date has been reached. Please register” and end program then.
This is not a good method (using SmartCheck (thanks a lot NuMega! (sarcassssm)) this is patched in no time).
How about having a few ‘EXE’ files?

  • Program.exe (this is just the main executable of your program)
  • Check.exe (name this FA12345.DLL or something)
  • Replace.exe (you can invent a name that isn’t very transparant…)
    Now, say you run program.exe and you see ‘hey, expired!’, what to do now?
    Shell Replace.exe and close program.exe
    Now in replace.exe you wrote code to delete program.exe (yes, delete), and rename FA12345.DLL to … yes program.exe)
    Now in Check.exe/FA12345.DLL (now called program.exe) you have code that just says: “Expired, sorry, you can no longer use this program”.
    Once the program has expired, they have NO more chance in cracking it.
    I would prefer working with the file in the windows directory, as if so, you can just check if the file is there upon installation, if so, don’t install, as your user has installed before).
    I hope I made myself clear on this matter.
  1. Using a serial
    This is an easy method when thinking of your users: they buy your program, you send them a string, they enter and they have the whole application.
    Great! Easy to program, not a lot of worries, but DAMN easy to crack.
    With crack I mean here: patch the program so it thinks every string is correct, or create a keygenerator, which is even worse.
    I am personally not fond of this method as it is not a good protection, although it is widely used.
    It is not very hard to do: write an algorithm that creates a serial, check it against the serial entered. That’s it.
    Well, upon right entrance of the serial, you should enable everything, but that’s not really a problem.

  2. Internet applications
    This is a solution almost exclusively for applications that need to be connected to the internet.

After registering, require your user to connect to the internet (maybe without him knowing it… I don’t like this idea really much as it makes me think of spyware , but hey it’s for security, keep in mind firewalls may block this)

Say you have a database on the internet with all registered users, usernames, pass and some other info to check against.
Now when someone with a cracked version does this check, you could easily capture him, not? (require him on registration to fill in a few forms (name, company, maybe OS)
Of course this IS crackable too, but a lot harder I believe (especially when you have an app that needs to be connected to the internet)

  1. Safest of them all!
    Don’t give out shareware. Only sell the full version, and use that idea from the first ‘chapter’: every application has a UNIQUE code, so if it is pirated, you can find who did it.

  2. Conclusion
    One conclusion can be made: securing your app is a damn hard job, as you can make the cracking process for the crackers too, but there will ALWAYS be a way to crack an application. A pity, but it is. sigh

By breakfast3001 at vbcity

I would’ve liked it if I was noticed my article was posted here :rolleyes:

Hi breakfast3001,

Sorry I used it for myself and I thought It was good so I posted it here. I try an give credit to the rightfull owner. Would you me to remove it? :eek:

No, you don’t have to remove it :wink:
I was just surprised finding it on the internet, I’m flattered you wanted to use it :wink: