Changes

526 bytes added ,  22:18, 21 December 2016
Line 265: Line 265:     
==Custom SpotPass content==
 
==Custom SpotPass content==
All data downloaded with SpotPass ''must'' use the signed+encrypted BOSS [[SpotPass|container]]. There doesn't seem to be any way to write to the SpotPass data stored in extdata via service commands either.
+
SpotPass supports raw content download without using the encrypted+signed SpotPass container(raw content is used by [[Home Menu]] SpotPass VersionList for example). However, this is incompatible with the data-loading method used with SpotPass-container content(NsData commands can't be used with it).
   −
Therefore, the only known ways to use custom SpotPass content(homebrew usage etc) is: "CFW" / ARM11-kernelhax with the sigchecks for this patched, or some sort of BOSS-sysmodule exploit if there's any vulns to begin with.
+
When writing the raw content, it firsts deletes and creates the "<taskID>" file under the data-storage extdata with normal extdata(not the separate boss archive). Once successful, the final filename specified by the task config will be deleted if needed, then the "<taskID>" file will be renamed to the final filename. Afterwards, the user-process can access the final file just like any other extdata file.
 +
 
 +
For using custom content with the SpotPass container(like official titles), the only known ways to do so is: "CFW" / ARM11-kernelhax with the sigchecks for this patched, or some sort of BOSS-sysmodule exploit if there's any vulns to begin with.
    
==HTTP upload==
 
==HTTP upload==