Cryptographic Token Interface Standard |
PKCS#11 |
The following table summarizes the kind of access each type of session has to each type of object. A given type of session has either read-only access, read/write access, or no access whatsoever to a given type of object.
Note that creating or deleting an object requires read/write access to it, e.g., a "R/O User Functions" session cannot create or delete a token object.
Table 6, Access to Different Types Objects by Different Types of Sessions
| |||||
Type of object | |||||
Public session object | |||||
Private session object | |||||
Public token object | |||||
Private token object |
As previously indicated, the access to a given session object which is shown in Table 6 is limited to sessions belonging to the application which owns that object (i.e., which created that object).