I've been reading up on the archives about various ways to do serial algorithms, and there are definitely lots of good ideas. If anyone knows the answers to any of these questions, it'd be much appreciated (I couldn't find it in the archives). I'm working on redoing a bit of my registration stuff - and realize it *will* be cracked regardless, but want to make it at least a little tough/fun for them...
1a) Having "include function names"=false, is obviously more ideal to deter hackers in final builds. From past discussions it seems that when set to false, method names are encoded in the binary in base64 - or maybe I read that wrong. Is this the case? 1b) In any case, if a cracker was attempting to figure out my registration system is there a benefit to naming methods and parameters odd things that don't raise attention as much. E.g. Would a function named "WaterTheLawn" be less likely to be noticed than one named "CheckSerialNumber"? 2) Another idea is to spread some data around the app in different places. Out of curiosity, what happens in the following cases: a) I have one module with 10 int properties. In the binary (or while it's running) are these stored in relatively consecutive blocks in memory? b) If I create 10 different modules with 1 int property in each, does this spread the space that they're stored in memory? 3) When someone is trying to decompile my app and watching it's output, if I have a function that declares 2 things: Dim a as string = "secret" dim a as new MemoryBlock(7) a.PString(0)="secret" //in real usage, I'd jumble it up a bit. But just for a simple example ...Would it be any easier/harder to get the value of either one of these? Hmm...that's about it for now. I'm sure I'll have more :) Thanks for any ideas, Chad _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
