6,263
edits
Changes
Jump to navigation
Jump to search
Line 258:
Line 258: + + + + +
no edit summary
==Content Data Storage==
==Content Data Storage==
SpotPass content for each application is stored under the extdata specified by [[BOSS:SetStorageInfo]]. That command and others verify that the PID associated with the current service session has access to the specified extdata by using [[FS:CheckAuthorityToAccessExtSaveData]], returning an error on failure. This basically renders SpotPass unusable under user-processes(when initialized under those processes) which don't have access to any SD extdata(unless NAND extdata is used instead).
SpotPass content for each application is stored under the extdata specified by [[BOSS:SetStorageInfo]]. That command and others verify that the PID associated with the current service session has access to the specified extdata by using [[FS:CheckAuthorityToAccessExtSaveData]], returning an error on failure. This basically renders SpotPass unusable under user-processes(when initialized under those processes) which don't have access to any SD extdata(unless NAND extdata is used instead).
==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.
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.
==BOSS Tasks==
==BOSS Tasks==