Pelican Police
Member
The documentation for ds_map_secure_save in GM2 states:
IMPORTANT! One of the features of a secure saved file is that it is locked to the device that it was created on, so you cannot load a file saved on one device into a project running on another device.
That's a pretty bold claim, so I was wondering how it achieves that? Or is that a GM2 secret that's better for everyone if it's not known...
Some of my guesses of what it could use to encrypt it would be:
- The username of the current user
- Meta information about computer hardware (but if the user upgrades, then save files corrupt?)
- A hidden key buried somewhere in the registry
- A hidden key stored in a file buried in some root folder / next to the .exe
I'm also assuming this feature is exclusive to GM2 given that the GM1 documentation doesn't claim this?
IMPORTANT! One of the features of a secure saved file is that it is locked to the device that it was created on, so you cannot load a file saved on one device into a project running on another device.
That's a pretty bold claim, so I was wondering how it achieves that? Or is that a GM2 secret that's better for everyone if it's not known...
Some of my guesses of what it could use to encrypt it would be:
- The username of the current user
- Meta information about computer hardware (but if the user upgrades, then save files corrupt?)
- A hidden key buried somewhere in the registry
- A hidden key stored in a file buried in some root folder / next to the .exe
I'm also assuming this feature is exclusive to GM2 given that the GM1 documentation doesn't claim this?