On 12/29/2009, at 09:24 PM, Benjamin Rister wrote: > Once there’s a keygen, you have no way of distinguishing a legit serial from > a non-legit serial using your algorithm, period. The only remedy is to change > to another algorithm, retroactively invalidating all of your paying customers > serials in the process. You can’t just start issuing new serials without > impacting existing customers, because again, you have no way of > distinguishing in the field whether this is a paid customer or not.
You have to phone home in this case. If this is a good practice is another question. > Or, you could do the other 99% of the work yourself to get 5% more crack > resistance from being slightly more differentiated, plus the risk that you > screwed something up along the way. If it’s that important to you and you > have that much knowledge and time, knock yourself out. =) Don’t get me wrong. I would never spend a lot of time with anti-piracy code, because I know how crackers tick. And I highly appreciate all of the existing Mac frameworks. But for people who are insane enough to fight against crackers it is still a better advice to tell them to write their own protection. From a business pov this is plain stupid. You don’t get any ROI spending all your time in anti-piracy code. Rafael Chief Sucker at Juicy Cocktail http://www.juicycocktail.com/ ------------------------------------ MacSB email guidelines: http://tinyurl.com/2g55d6 Use MacSB-Talk for off topic messages: http://groups.google.com/group/macsb-talk Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/macsb/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/macsb/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
