quote: Original post by Joker2000
You do realize that the whole point is to write the file in a format the user CANNOT read to prevent him from changing values and such, right? Will >> and << still "encrypt" them if I'm using ios::binary?
---
Joker2000
Stevie Ray Vaughan - The Legend
The user, for the time being, is you. Thus being able to edit,
and more importantly read save games is a good thing. Simply
writing your save games as binaries provides no difficulty
whatsoever to those who wish to cheat. It saves disk space and
is often faster, but provides no security. If you want to
prevent people from editing your files, use a checksum that's
difficult to guess, or, even better, use some form of
error-correcting code. This will confuse most kids with hex
editors and even add safety. Then, if you are still paranoid use
legal strength DES/TwoFish and obsfucate the key.
It might take a month or two before some determined kid has a
save game editor up. The thing is, get it working first, and
make it easy to work with.
Edited by - Grib on July 25, 2000 5:56:50 PM