2 .\" Copyright (c) 2005, Sun Microsystems, Inc. All Rights Reserved.
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH PKCS11_KERNEL 5 "Oct 27, 2005"
8 pkcs11_kernel \- PKCS#11 interface to Kernel Cryptographic Framework
12 /usr/lib/security/pkcs11_kernel.so
13 /usr/lib/security/64/pkcs11_kernel.so
19 The \fBpkcs11_kernel.so\fR object implements the RSA PKCS#11 v2.20
20 specification by using a private interface to communicate with the Kernel
21 Cryptographic Framework.
24 Each unique hardware provider is represented by a PKCS#11 slot. In a system
25 with no hardware Kernel Cryptographic Framework providers, this PKCS#11 library
29 The PKCS#11 mechanisms provided by this library is determined by the available
33 Application developers should link to \fBlibpkcs11.so\fR rather than link
34 directly to \fBpkcs11_kernel.so\fR. See \fBlibpkcs11\fR(3LIB).
37 All of the Standard PKCS#11 functions listed on \fBlibpkcs11\fR(3LIB) are
38 implemented except for the following:
56 A call to these functions returns \fBCKR_FUNCTION_NOT_SUPPORTED\fR.
59 Buffers cannot be greater than 2 megabytes. For example, \fBC_Encrypt()\fR can
60 be called with a 2 megabyte buffer of plaintext and a 2 megabyte buffer for the
64 The maximum number of object handles that can be returned by a call to
65 \fBC_FindObjects()\fR is 512.
68 The maximum amount of kernel memory that can be used for crypto operations is
69 limited by the \fBproject.max-crypto-memory\fR resource control. Allocations in
70 the kernel for buffers and session-related structures are charged against this
75 The return values of each of the implemented functions are defined and listed
76 in the RSA PKCS#11 v2.20 specification. See http://www.rsasecurity.com.
80 See \fBattributes\fR(5) for a description of the following attributes:
88 ATTRIBUTE TYPE ATTRIBUTE VALUE
90 Interface Stability Standard: PKCS#11 v2.20
93 MT-Safe with exceptions. See section 6.5.2 of RSA PKCS#11 v2.20
100 \fBcryptoadm\fR(1M), \fBrctladm\fR(1M), \fBlibpkcs11\fR(3LIB),
101 \fBattributes\fR(5), \fBpkcs11_softtoken\fR(5)
104 RSA PKCS#11 v2.20 http://www.rsasecurity.com
108 Applications that have an open session to a PKCS#11 slot make the corresponding
109 hardware provider driver not unloadable. An administrator must close the
110 applications that have an PKCS#11 session open to the hardware provider to make
111 the driver unloadable.