2010-09-16, 07:28 PM
Security is a lie.
The best you can do is protect something briefly, because the number of people who want in outnumber the amount of resources you can devote to preventing access.
There's virtually no way to make a product that can't be bypassed.
You add a CRC check to the program? Cracker changes the hash value it hunts for as part of the bypass.
You add a vpn check like you suggested, Cracker disables the check entirely, writes a local proxy for it, or otherwise bypasses it.
You use a basic serial number and regardless of how complex it is a cracker can decode what it's looking for and make a keygen for it because the program itself has to know what mix of parameters are acceptable and can be coerced into giving you the keys.
You use a combination approach and the cracker just applies a mix of all the above.
You add in a check every time it gets used to validate it as part of the check for updates, cracker just NOOPs that.
You only release full versions to paying customers via download or media, someone's gonna leak it, likely repacked minus any identifying info you may have put there to catch potential leaks.
This is a very dangerous topic to skirt here as we don't condone discussion regarding warez, but neither will we deny that's impossible to prevent or avoid.
The best you can do is protect something briefly, because the number of people who want in outnumber the amount of resources you can devote to preventing access.
There's virtually no way to make a product that can't be bypassed.
You add a CRC check to the program? Cracker changes the hash value it hunts for as part of the bypass.
You add a vpn check like you suggested, Cracker disables the check entirely, writes a local proxy for it, or otherwise bypasses it.
You use a basic serial number and regardless of how complex it is a cracker can decode what it's looking for and make a keygen for it because the program itself has to know what mix of parameters are acceptable and can be coerced into giving you the keys.
You use a combination approach and the cracker just applies a mix of all the above.
You add in a check every time it gets used to validate it as part of the check for updates, cracker just NOOPs that.
You only release full versions to paying customers via download or media, someone's gonna leak it, likely repacked minus any identifying info you may have put there to catch potential leaks.
This is a very dangerous topic to skirt here as we don't condone discussion regarding warez, but neither will we deny that's impossible to prevent or avoid.