|Cryptographic Token Interface Standard||
This RSA Security Inc. Public-Key Cryptography Standards (PKCS) document was produced from the original standard document using Open Office to export it in MediaWiki format then processed through some custom perl scripts and then passed into a modified version of doxygen to finally produce the HTML output. The text of the standard is otherwise unchanged.
Tim Hudson - firstname.lastname@example.org - 10-Sep-2009
As public-key cryptography begins to see wide application and acceptance, one thing is increasingly clear: If it is going to be as effective as the underlying technology allows it to be, there must be interoperable standards. Even though vendors may agree on the basic public-key techniques, compatibility between implementations is by no means guaranteed. Interoperability requires strict adherence to an agreed-upon standard format for transferred data.
Towards that goal, RSA Laboratories has developed, in cooperation with representatives of industry, academia and government, a family of standards called Public-Key Cryptography Standards, or PKCS for short.
PKCS is offered by RSA Laboratories to developers of computer systems employing public-key technology. It is RSA Laboratories' intention to improve and refine the standards in conjunction with computer system developers, with the goal of producing standards that most if not all developers adopt.
The role of RSA Laboratories in the standards-making process is four-fold:
The PKCS family currently includes the following documents:
PKCS #1: RSA Encryption Standard. Version 1.5, November 1993.
PKCS #3: Diffie-Hellman Key-Agreement Standard. Version 1.4, November 1993.
PKCS #5: Password-Based Encryption Standard. Version 1.5, November 1993.
PKCS #6: Extended-Certificate Syntax Standard. Version 1.5, November 1993.
PKCS #7: Cryptographic Message Syntax Standard. Version 1.5, November 1993.
PKCS #8: Private-Key Information Syntax Standard. Version 1.2, November 1993.
PKCS #9: Selected Attribute Types. Version 1.1, November 1993.
PKCS #10: Certification Request Syntax Standard. Version 1.0, November 1993.
PKCS #11: Cryptographic Token Interface Standard. Version 1.0, April 1995.
PKCS documents are available by sending electronic mail to <email@example.com> or via anonymous ftp to ftp.rsa.com in the pub/pkcs directory. There is an electronic mailing list, <firstname.lastname@example.org>, for discussion of issues relevant to the "next generation" of the PKCS standards. To subscribe to this list, send e-mail to <email@example.com> with the line "subscribe pkcs-tng" in the message body. To unsubscribe, send e-mail to <firstname.lastname@example.org> with the line "unsubscribe pkcs-tng" in the message body.
There is also an electronic mailing list, <email@example.com>, specifically for discussion of PKCS #11. To subscribe to this list, send e-mail to <firstname.lastname@example.org> with the line "subscribe cryptoki" in the message body. To unsubscribe, send e-mail to <email@example.com> with the line "unsubscribe cryptoki" in the message body.
Comments on the PKCS documents, requests to register extensions to the standards, and suggestions for additional standards are welcomed. Address correspondence to:
PKCS Editor RSA Laboratories 100 Marine Parkway, Suite 500 Redwood City, CA 94065 415/595-7703 fax: 415/595-4126 E-mail: firstname.lastname@example.org
It would be difficult to enumerate all the people and organizations who helped to produce PKCS #11. RSA Laboratories is grateful to each and every one of them. Especial thanks go to Bruno Couillard of Chrysalis-ITS and John Centafont of NSA for the many hours they spent writing up parts of this document.
For v1.0, PKCS #11's document editor was Aram Perez of International Computer Services, under contract to RSA Laboratories; the project coordinator was Burt Kaliski of RSA Laboratories. For v2.0, Ray Sidney served as document editor and project coordinator.