Matches in DBpedia 2014 for { ?s ?p In cryptography, PKCS #11 is one of the family of standards called Public-Key Cryptography Standards (PKCS), originally published by RSA Laboratories, that defines a platform-independent API to cryptographic tokens, such as hardware security modules (HSM) and smart cards. (The PKCS #11 standard names the API "Cryptoki" which is an amalgamation of "cryptographic token interface" and is pronounced as "crypto-key", but "PKCS #11" is often used to refer to the API as well as the standard that defines it.)Since there isn't a single standard for cryptographic tokens, this API has been developed to be an abstraction layer for the generic cryptographic token. The PKCS #11 API defines most commonly used cryptographic object types (RSA keys, X.509 Certificates, DES/Triple DES keys, etc.) and all the functions needed to use, create/generate, modify and delete those objects.PKCS #11 is largely adopted to access smart cards and HSMs. Most commercial certificate authority software uses PKCS #11 to access the CA signing key or to enroll user certificates. Cross-platform software that needs to use smart cards uses PKCS #11, such as Mozilla Firefox and OpenSSL (using an extension). Software written for Microsoft Windows may use the platform specific MS-CAPI API instead.. }
Showing items 1 to 1 of
1
with 100 items per page.
- PKCS_11 abstract "In cryptography, PKCS #11 is one of the family of standards called Public-Key Cryptography Standards (PKCS), originally published by RSA Laboratories, that defines a platform-independent API to cryptographic tokens, such as hardware security modules (HSM) and smart cards. (The PKCS #11 standard names the API "Cryptoki" which is an amalgamation of "cryptographic token interface" and is pronounced as "crypto-key", but "PKCS #11" is often used to refer to the API as well as the standard that defines it.)Since there isn't a single standard for cryptographic tokens, this API has been developed to be an abstraction layer for the generic cryptographic token. The PKCS #11 API defines most commonly used cryptographic object types (RSA keys, X.509 Certificates, DES/Triple DES keys, etc.) and all the functions needed to use, create/generate, modify and delete those objects.PKCS #11 is largely adopted to access smart cards and HSMs. Most commercial certificate authority software uses PKCS #11 to access the CA signing key or to enroll user certificates. Cross-platform software that needs to use smart cards uses PKCS #11, such as Mozilla Firefox and OpenSSL (using an extension). Software written for Microsoft Windows may use the platform specific MS-CAPI API instead.".