Leak Protection

[ChaosOverlord]

Couldnt you add in a function into releases (tools mostly) where the tool checks the computer name or something? Basically you modify a custom version of your program to every person who buys it, and if they try to distribute it then the person on the receiving end wont work unless they have the same computer and computer account name? You could easily have it authorize itself in many ways, then nobody could ever leak it.

[Wizatek]

Such things are very easy to bypass, usually by just changing 1 byte in the executable.

[ChaosOverlord]

How is that possible? Changing one byte can cancel out the effects of this?

Private Sub Form1_Load() Handles MyBase.Load
If My.Computer.Name <> "SpecificComputerNameHere" And My.User.Name <> "SpecificUserNameHere" Then : End : End If
End Sub
 

 

[Wizatek]

change the to == and its bypassed

[HateMe]

if then you should make an online check system what sends packets to an server and get packets back and packets with DES protection also, and not only use one check system also check random while the tool is running this makes it harder to bypass but its still not so hard, but many ppl will give up at this part, but if there someone realy want it bad to be cracked he will get it cracked

[luoo]

or make a hardwareid check and pack the program with smartassembly

[IronMan]

There is only one way to protect a binary from being shared to unwanted people. And thats using the strongest protector possible to pack your executable. I personally use a protector that only one person in the entire world has been known to unpack. Sending packets to server as HateMe describes is easy to bypass as well. As all you would have to do is just jump over that entire instruction. This is why executable protectors exist in the first place. You can add all the checks you want in your code, even send triple DES encrypted packets to authenticate with a server. Tho all of them are equally easily bypassed if your executable is not protected. Adding them checks into your code, and distributing your application without protecting it. Is essentially the same as giving out the source code to hackers. Worry about a protector first, then you can code in your own checks later. As once packed you cant alter the programs byte instructions without unpacking it, if you can unpack it.