Difference between revisions of "Applications"
Devnoname120 (talk | contribs) (Swapped Module <-> Library, see revision 1.1 under "Revision History" of "Vita SDK specifications" (https://wiki.henkaku.xyz/vita/File:Vita_SDK_specifications.pdf) |
|||
| Line 7: | Line 7: | ||
Most applications do not have the special [[Authentication ID|authentication id]] to access files outside of their own sandboxed directory. Applications access their own resources through <code>app0</code>, which is mounted to point to their own directory and is also mounted as read only (applications cannot modify their own resources). Certain virtual partitions can be accessed on demand as specified by the [[SDK]]. Some examples include <code>photo0</code> and <code>savedata0</code>. However, there is no way to mount actual partitions like <code>ux0</code> (memory card). | Most applications do not have the special [[Authentication ID|authentication id]] to access files outside of their own sandboxed directory. Applications access their own resources through <code>app0</code>, which is mounted to point to their own directory and is also mounted as read only (applications cannot modify their own resources). Certain virtual partitions can be accessed on demand as specified by the [[SDK]]. Some examples include <code>photo0</code> and <code>savedata0</code>. However, there is no way to mount actual partitions like <code>ux0</code> (memory card). | ||
| − | === Shared | + | === Shared Module ASLR === |
| − | Since 2.06, user shared | + | Since 2.06, user shared modules like [[SceLibKernel]] are loaded to randomized addresses. The randomization was later improved to be more random in 2.60. |
=== Application ASLR === | === Application ASLR === | ||
| Line 14: | Line 14: | ||
=== NID Poisoning === | === NID Poisoning === | ||
| − | Perhaps as a direct result of [[UVLoader]] being open source, in 2.11, Sony replaces all entries in the [[ | + | Perhaps as a direct result of [[UVLoader]] being open source, in 2.11, Sony replaces all entries in the [[Modules#Imports|library import table]] with junk data. This prevents disclosure of [[Syscalls|syscalls]] based on their NIDs. |
=== Syscall Randomization === | === Syscall Randomization === | ||
| Line 20: | Line 20: | ||
== List of System Applications == | == List of System Applications == | ||
| − | See [[ | + | See [[Modules#System Applications|here]]. |
[[Category:System]] | [[Category:System]] | ||
Revision as of 23:37, 8 November 2016
Security
Authentication ID
Applications running on the Vita are subject to restrictions based off of their authentication ids. Certain syscalls can only be called by applications that have permission to call it. For example, SceShell can make certain calls to install packages or mount file systems that games can't. Therefore an userland exploit is more valuable in a system application like CMA or SceShell because regular games and applications do not have access to many syscalls.
File System Sandbox
Most applications do not have the special authentication id to access files outside of their own sandboxed directory. Applications access their own resources through app0, which is mounted to point to their own directory and is also mounted as read only (applications cannot modify their own resources). Certain virtual partitions can be accessed on demand as specified by the SDK. Some examples include photo0 and savedata0. However, there is no way to mount actual partitions like ux0 (memory card).
Since 2.06, user shared modules like SceLibKernel are loaded to randomized addresses. The randomization was later improved to be more random in 2.60.
Application ASLR
Since 2.60, user applications (the main library) themselves can be compiled with ASLR support. Although not all games and applications choose to use this feature of the compiler, more and more are.
NID Poisoning
Perhaps as a direct result of UVLoader being open source, in 2.11, Sony replaces all entries in the library import table with junk data. This prevents disclosure of syscalls based on their NIDs.
Syscall Randomization
Syscall numbers are not statically assigned. On each boot, the same kernel module exports will have different syscall numbers. However, the delta between syscall exports from the same module are the same, so in theory if you can identify one syscall from a module, you can calculate all the other syscalls.
List of System Applications
See here.