🚀 go-pugleaf

In article <5cgqmo$h...@chronicle.concentric.net>, boomer*@cris.com* (MikeM) wrote:
>>Pas...@Globalserve.net (FraggyBalls) wrote:
>
>much better (and simpler idea)... when logging in, have the server
>check the s/w to see if it's been tampered with. 
>
>For example.. as my character develops, an algorithym creates an
>encripted checksum.  When I log in, the same algorithym on the host
>looks at my stats, etc and generates a checksum.
>
>If the checksums don't match.. then I'm not allowed to log in (or only
>log into special 'cheaters' arena).
>

Its actually fairly difficult to tamper with the savegame files, which is what 
this solution protects againsts.

What's easier is poking values into the program's global variables while the 
game is running.

Having the critical stats on the server, combined with double-entry 
(or more extensive accounting protections) of variables, makes it much more 
difficult to tamper with characters

You can use MS CryptoAPI for the network messages.  You can encrypt 
memory variables (map 1 byte across 8 bytes of memory, with non data elements 
acting as validation bits (computed based on values of other stats))

The point is the security could be much better.  Force hackers to decompile 
and understand the assembler program flow.