• Content count

  • Joined

  • Last visited

Community Reputation

123 Neutral

About Octarinne

  • Rank
  1. Quote:Original post by Servant of the Lord Sounds cool, but what's to prevent a hacker from just copying the program, with the same serial key? Couldn't he just distribute his key with his version of the program? You're right. He could. You could always link the serial to the hard disk of the user but I personally don't like this since I like to be able to install software after a long time on a new system. The technique I am proposing is not 100% efficient but it's the most effective technique I could come up with that isn't penalizing to a legitimate user. Quote:Even if a developer makes the serial key "call home" to verify it's not been used before, the hacker could merely disable the call home part, and the whole thing falls apart. (Security is only as strong as the weakest link - break the weakest part and everything else doesn't matter) The call home thing is for program that require an on-line connection to use like on-line games for example. My technique would ensure that only legitimate users could connect. Still, without my technique if the server checks for a correct serial it should avoid piracy as far as I know. Quote:Wouldn't a better idea be to use source comments, and do something like this: ..code I don't want protected (due to speed issues or whatever). //<YarrBuster> ..code that Yarr buster can mess with. //</YarrBuster> ..code I don't want encrypted. Yes it would, excellent idea. The source I have provided is only a prototype to demonstrate how the protection works, there's room for improvements. Thanks for your comments and suggestion!
  2. Hello, I've been working on a protection technique that I think has never been tried. I protects a program by encoding the serial protection in the source and generating a unique .exe for every user. Each serial can only be used with the corresponding .exe. If you want to see some source and know more about this technique, please visit the Yarr Buster site here: http://software.collectionsbp.com/YarrBuster/ and let me know what you think here!
  3. Hello, since I have no more time for now to work on my almost complete 2D engine (still work to be done and few bugs to eradicate), I'm offering the VB6 SP3 source code here. It's old but nice. You can learn a little about the engine here: http://www.gamedev.net/community/forums/topic.asp?topic_id=527828 Here's the source link: http://prezeau.net/Engine/My2DEngine20100526.zip and here's a screen shot: Make sure to read the Read this first.doc file!!! Enjoy!
  4. basic copy proection

    Extrarius: There would be more than the registration number that would be encrypted. All the text in the exe and data files. They would be encrypted with the checksum of the user's name wich itself would be encrypted with the checksum of the exe. So if someone tempers with the exe, all the data won't work anymore. And you can't use NOPs to prevent anything since the data must be used for the program to work. And if you compare the exe and data files from 2 registered copies, all the data and text in the exe will be different from the 2 copies. This will make the registration number rather hard to find. May be gamedev should hold a copy protection contest just for the fun of it... ;-)
  5. basic copy proection

    Caculate the checksum of your exe except for the parts that contain strings of text. Also include a string that will be used to display the registrant's name thanking him for his support. When someone registers the game, encode his name and registration number (separatly), put the encoded strings in the exe (make a small program that will only do this). Calculate the checksum of the registered name and encode the other strings in your exe (and possibly data files) with the checksum (with the same small program). When the user starts the program he will see the thank you message with his name. If the user finds the name string and tries to modify it, suddenly the text and data files won't be decoded properly (since they are encrypted with the user's name). If the user succeeds in cracking the protection, you will still be able to decode the registration number that is secretly hiding encrypted somewhere in the exe. You can go a step further by including random strings when encoding your exe to make it harder to find the data that is modified with different exes. This won't stop piracy but it should help you know who distributed the program if it's massively distributed. Unfortunately if someone registers with false informations, you are toast. This solution requires a lot of work, probaly more than what you may gain from it. But it could prevent the people who have limited knowledge of computers from copying it. --------------------------- Visit www.collectionsbp.com