| WilliamWatts said: You're assuming they aren't familiar with that method to counter-act this type of system because???? |
Because any methods to counter-act this exist in the code that is being modified anyway (which is why DRM is fundamentally flawed).
Here is a basic runthrough of how the crackers will get around "remote" saving:
1) Trace the packets between the client and the server. If what is sent to the server is the same as what is returned (i.e the client produces the save then just sends it to the server), then all I need to do is get the client to connect to my local server which saves off the packet and sends it back when asked. This is probably all they will actually be doing.
2) If the packets differ, figure out if its some sort of encryption.
2a) If it is encrypted, remove the encryption and decryption algorithms from the client and get it sending the raw save to my local server.
3) If the return packet differs (after decryption if required) then look at how the client processes this packet and map the original packets contents to the return packet.
4) If keen, they can also try and modify the client to write directly to a file instead, however the server method would allow a more generic solution for other games using the same system.
If there are any mechanics to detect modification beyond the already modified functionality they shall just be removed/modified anyway.
