PureBasic Forums - English

A solution, concists to tag the prg and eventually the files generated by your application

With a simple customer number!
Which represents the customer's name, address,
This client number, is listed in your personal database

So if you find a hacker version of the software, you read the magic number, and you know which client is responsible for the leak!

More than making justice work

Of course, you explain to your client, that the prg is dedicated to his person ...
And also, add several random numbers to avoid comparisons between 2 prg

dobro wrote:you know which client is responsible for the leak!

Except anonymous pirates don't care if you know, because they use stolen credit cards to buy and share your app.

Dude wrote:

dobro wrote:you know which client is responsible for the leak!

Except anonymous pirates don't care if you know, because they use stolen credit cards to buy and share your app.

They don't have to.. Full version is behind paywall.. No license holder no binary to crack.. Generate nonce each version to salt license holder data and embed it in installer-script or binaries or both..

Go on any warez forum or torrent site and look for PureBASIC 5.60. It uses this model.

If you get an insanely good PE, ELF, or MACH protector people will crack it for fun.. I've seen protections made by talented crackers get cracked, and it was better than what is on 2017 AAA games and industrial tools like Denuvo and HASP.