Anti Savegame Restore: Difference between revisions

(8 intermediate revisions by 6 users not shown)

Line 3:

=Implementation=

When creating the SD savedata, the application generates a random u64 value, then stores it in an arbitary savefile in the savegame FS. The application then uses the anti-savegame-restore [[Filesystem_services|FS]] commands to verify the stored u64(with the u64 loaded by FS module), and to update the u64 used by FS module. The u64 used by FS module is stored in ~~a NAND savegame~~.

When creating the SD savedata, the application generates a random u64 value, then stores it in an arbitary savefile in the savegame FS. The application then uses the anti-savegame-restore [[Filesystem_services|FS]] commands to verify the stored u64(with the u64 loaded by FS module), and to update the u64 used by FS module. The u64 used by FS module is stored in the FS module [[System_SaveData]].

Each time the application writes to the savegame, the u64 value stored in the savefile should be updated(and the command for updating the NAND u64 value should be used as well). Usually applications update this value by incrementing it, however generating a new random-number or other methods of updating it can be used as well.

=Remove the secure value=

It is possible to remove the secure value easily by using [[FS:ControlSecureSave|ControlSecureSave]], from the [[Filesystem_services#Filesystem_service_.22fs:USER.22|fs:USER]] service, with the [[FS:ControlSecureSave#Action|SECURESAVE_ACTION_DELETE]] action.

=Applications using this feature=

* Animal Crossing: New Leaf

* Pokemon X & Y

* Pokemon Omega Ruby & Alpha Sapphire

It's ~~currently unknown whether there's any eShop-only titles that use this.~~

* Pokemon Omega Ruby & Alpha Sapphire Demo

* Pokemon Shuffle

* Super Smash Bros

* Pokemon Red,Blue and Yellow (GB(C) VC)

* Rusty's Real Deal Baseball

* Megami Meguri

@@ Line 3: / Line 3: @@
 =Implementation=
-When creating the SD savedata, the application generates a random u64 value, then stores it in an arbitary savefile in the savegame FS. The application then uses the anti-savegame-restore [[Filesystem_services|FS]] commands to verify the stored u64(with the u64 loaded by FS module), and to update the u64 used by FS module. The u64 used by FS module is stored in a NAND savegame.
+When creating the SD savedata, the application generates a random u64 value, then stores it in an arbitary savefile in the savegame FS. The application then uses the anti-savegame-restore [[Filesystem_services|FS]] commands to verify the stored u64(with the u64 loaded by FS module), and to update the u64 used by FS module. The u64 used by FS module is stored in the FS module [[System_SaveData]].
 Each time the application writes to the savegame, the u64 value stored in the savefile should be updated(and the command for updating the NAND u64 value should be used as well). Usually applications update this value by incrementing it, however generating a new random-number or other methods of updating it can be used as well.
+=Remove the secure value=
+It is possible to remove the secure value easily by using [[FS:ControlSecureSave|ControlSecureSave]], from the [[Filesystem_services#Filesystem_service_.22fs:USER.22|fs:USER]] service, with the [[FS:ControlSecureSave#Action|SECURESAVE_ACTION_DELETE]] action.
 =Applications using this feature=
 * Animal Crossing: New Leaf
 * Pokemon X & Y
+* Pokemon Omega Ruby & Alpha Sapphire
-It's currently unknown whether there's any eShop-only titles that use this.
+* Pokemon Omega Ruby & Alpha Sapphire Demo
+* Pokemon Shuffle
+* Super Smash Bros
+* Pokemon Red,Blue and Yellow (GB(C) VC)
+* Rusty's Real Deal Baseball
+* Megami Meguri