Search results

...processor. By convention, a finalized SM filename ends with "_sm.self". A SM is usually unloadable and is only loaded when one of its exported functions = Secure Modules List =

...l module that is primarily responsible for calling [[Secure_Modules|Secure Modules]] functions. SceUInt32 self_type; // kernel = 0, user = 1, SM = 2, 0x10, 0x100, ?0x10001 main user process?

== PS Vita modules == ...lModulemgr]] module, itself loaded by the [[NSKBL]]. Most PS Vita [[Secure Modules]] are loaded by the [[Secure Kernel]].

...sm.self, kernel PRX keys are located in kprx_auth_sm.self, Secure Modules (SM) as well as kernel_boot_loader.self, are located in secure_kernel.enp).

4 = SM loading 5 = SM loaded

...hen makes a request to [[TrustZone]] to load a new [[Secure_Modules|Secure Modules]] (to have the right keys and the right program to parse the data format). ...and a signed revoke list is passed early during startup (in [[TrustZone]] modules initialization), it is possible to revoke just about anything on the system

| 98 || level or self_type || SM || ...0x42 || For usermode self_type, requires QA flag 0xD mask 2. For kernel or SM self_type, requires QA flag 0xE mask 1.

Depending on the [[Secure_Modules|Secure Modules]] that is currently loaded, different commands are handled. | Command return value is written here by the SM

| 0x19BC || 0x4 || SM communication ID (obtained with sceSblSmCommStartSm) [[Category:Modules]]

| Allow to bypass absent Media Type 7 (host0:) in SELF attribute for Kernel/SM SELF. | Allow Remote SM Loading (host0:), Allow Remote Spfso Auth (host0:), Allow Remote FwLoader p

The use of os0:sm/gcauthmgr_sm.self is to support the new generation of Kirk. It uses a simil ...58B9]]. It appears that data from <code>aimgr_sm.self</code> (see [[Secure Modules Functions]]) along with <code>pOpt</code>, <code>rtc_tick</code> (the RTC i

...00A|encdec_w_portability_sm command 0x1000A]]. That is because anyway this SM command is not implemented in release System Software. [[Category:Modules]]

SceKernelModulemgr is in charge of loading both user modules and kernel modules. SceKernelModulemgr calls [[SceSblAuthMgr]] functions for the SELF decrypti ..._type</code> to 1 if decrypting a usermode module else 0 for kernel (2 for SM but maybe not allowed).

...|kernel load sequence]] and its libraries are imported by almost all other modules. See [[Virtual Memory]] and [[Physical Memory]] for more details on the mem Maybe sets a pointer to the library stub structure. See [[Modules]].