thanks for the good advice!
On Jan 14, 2:34 pm, "Wojciech S. Czarnecki" <[email protected]> wrote: > Dnia Thu, Jan 14, 2010 at 02:59:20PM -0800, wesker napisa (a): > > > Thanks for the feedback, I hadn't considered that. > > > I just want a simple approach that doesn't make it TOO easy to crack. > > If someone does crack it, fine, they've earned it, I just prefer they > > work for their copy. :) > > > Would you have any simpler recommendations? > > simplest: use hard coded symmetric key using crypto api of OS to > obscure id. For cracker its same easy work, for you its a matter > of few lines of code instad of learning public key crypto. > > There is more freely avaliable similar schemes. But all of them, > after stripping bad logic, equals above. All of them need > guy with disassembler a cola sixpack and two pizzas. Done. > > If you would more protection, use your customer credit card > data and machine id to customize executable. And then use > checksum of this as constant with many critical or showy > computations. > > No encryption, harder to patch, easier to omit place to patch > what will result in malfunctions of stolen copy. > > Just dont yell when your app will get bad opinion, and > prepare enough money for support folks. People are > changing their machines or components quite frequent. > > Kind regards, Ohir. > > -- > > Wojciech S. Czarnecki > << ^oo^ >> OHIR-RIPE
-- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com.
