--- schema-version: v1.2.9 id: OASISPKCS11-Profiles-v2.40 title: - content: 'PKCS #11 Cryptographic Token Interface Profiles Version 2.40' language: - en script: - Latn format: text/plain type: main link: - content: http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/os/pkcs11-profiles-v2.40-os.html type: src - content: http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/os/pkcs11-profiles-v2.40-os.pdf type: pdf - content: http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.40/os/pkcs11-profiles-v2.40-os.doc type: doc type: standard docid: - id: OASIS PKCS11-Profiles-v2.40 type: OASIS primary: true docnumber: PKCS11-Profiles-v2.40 date: - type: issued value: '2015-04-14' contributor: - organization: name: - content: OASIS contact: - uri: https://www.oasis-open.org/ role: - description: - content: Standards Development Organization type: authorizer - type: publisher - organization: name: - content: OASIS PKCS 11 TC contact: - uri: https://www.oasis-open.org/committees/pkcs11/ role: - description: - content: Committee type: authorizer - person: name: given: forename: - content: Robert language: - en script: - Latn surname: content: Griffin language: - en script: - Latn affiliation: - organization: name: - content: EMC Corporation contact: - uri: http://www.emc.com/ contact: - email: robert.griffin@rsa.com role: - description: - content: Chair type: editor - person: name: given: forename: - content: Valerie language: - en script: - Latn surname: content: Fenwick language: - en script: - Latn affiliation: - organization: name: - content: Oracle contact: - uri: http://www.oracle.com/ contact: - email: valerie.fenwick@oracle.com role: - description: - content: Chair type: editor - person: name: given: forename: - content: Tim language: - en script: - Latn surname: content: Hudson language: - en script: - Latn affiliation: - organization: name: - content: Cryptsoft Pty Ltd. contact: - uri: http://cryptsoft.com/ contact: - email: tjh@cryptsoft.com role: - type: editor language: - en script: - Latn abstract: - content: |- Intended for developers and architects who wish to design systems and applications that conform to the PKCS #11 Cryptographic Token Interface standard. The PKCS #11 Cryptographic Token Interface standard documents an API for devices that may hold cryptographic information and may perform cryptographic functions. language: - en script: - Latn format: text/plain doctype: type: standard editorialgroup: - name: OASIS PKCS 11 TC ext: schema-version: v1.0.1 technology_area: - Privacy/Identity - Security