For example, a smart card reader would represent a slot and the smart card would represent the token. It is also possible that multiple slots may share the same token. Figure 1: General PKCS#11 Model. Within PKCS#11, a token is viewed as a device that stores objects and can perform cryptographic functions. The token was removed from its slot during the execution of the function.
PKCS#11 is used as a low-level interface to perform cryptographic operations without the need for the application to directly interface a device through its driver. PKCS#11 represents cryptographic devices using a common model referred to simply as a token. An application can therefore perform cryptographic operations on any device or token, using the same independent command set.
The PKCS #11 API, also known as Cryptoki, includes a suite of cryptographic services for encryption, decryption, signature generation, signature verification, and permanent key storage. The software found on the installation DVD is compliant with PKCS #11 v. 2.20. The latest versions of the client software and HSM firmware can be found on the Thales Technical Support Customer Portal. See Support Contacts for more information.
>SafeNet ProtectServer Network HSM
HSMs include high-speed DES and RSA hardware acceleration, as well as generic security processing. Secure, persistent, tamper-resistant CMOS key storage is included. Multiple adapters may be used in a single host computer to improve throughput or to provide redundancy. HSMs may be installed locally, on the same host system as SafeNet ProtectToolkit-C or they may be located remotely across a network.
>PCI mode in conjunction with a locally-installed SafeNet ProtectServer PCIe HSM.
A machine with a SafeNet ProtectServer PCIe HSM installed may also be used as a server in network mode.
Within the client/server runtime environment, the server performs cryptographic processing at the request of the client. The server itself will only operate in one of the hardware runtime modes.
Runtime Licensing
Please refer to the readme.txt file found in the install directory of the SafeNet ProtectToolkit-C SDK for licensing requirement details.
Within PKCS#11, a token is viewed as a device that stores objects and can perform cryptographic functions. Objects are generally defined in one of four classes:
>Certificate objects, which are digital certificates such as X.509
>Vendor-defined objects
A connection between a token and an application is referred to as a session. Session objects are temporary and only remain in existence while the session is open. Session objects are only ever visible to the application that created them.
Is Roulette Legal In Arizona