Print this page
6414175 kcf.conf's supportedlist not providing much usefulness
   1 #
   2 # CDDL HEADER START
   3 #
   4 # The contents of this file are subject to the terms of the
   5 # Common Development and Distribution License (the "License").
   6 # You may not use this file except in compliance with the License.
   7 #
   8 # You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
   9 # or http://www.opensolaris.org/os/licensing.
  10 # See the License for the specific language governing permissions
  11 # and limitations under the License.
  12 #
  13 # When distributing Covered Code, include this CDDL HEADER in each
  14 # file and include the License file at usr/src/OPENSOLARIS.LICENSE.
  15 # If applicable, add the following below this CDDL HEADER, with the
  16 # fields enclosed by brackets "[]" replaced with your own identifying
  17 # information: Portions Copyright [yyyy] [name of copyright owner]
  18 #
  19 # CDDL HEADER END
  20 #
  21 #
  22 # Copyright 2007 Sun Microsystems, Inc.  All rights reserved.
  23 # Use is subject to license terms.
  24 #
  25 # ident "%Z%%M% %I%     %E% SMI"
  26 #
  27 # /etc/crypto/kcf.conf
  28 #
  29 # Do NOT edit this file by hand.   An administrator should use cryptoadm(1m)
  30 # to administer the cryptographic framework.  A developer for a kernel software
  31 # provider package or a cryptographic provider device driver(s) package should
  32 # provide an input file and use the {i,r}.kcfconf class action scripts to
  33 # update this file during the installation and removal of the package.
  34 #
  35 # This document does not constitute an API.  The /etc/crypto/kcf.conf file may
  36 # not exist or may have a different content or interpretation in a future 
  37 # release.  The existence of this notice does not imply that any other 
  38 # documentation that lacks this notice constitutes an API.
  39 #
  40 #  
  41 #       
  42 # Start SUNWcsr
  43 des:supportedlist=CKM_DES_CBC,CKM_DES_ECB,CKM_DES3_CBC,CKM_DES3_ECB
  44 aes:supportedlist=CKM_AES_ECB,CKM_AES_CBC,CKM_AES_CTR
  45 arcfour:supportedlist=CKM_RC4
  46 blowfish:supportedlist=CKM_BLOWFISH_ECB,CKM_BLOWFISH_CBC
  47 ecc:supportedlist=CKM_EC_KEY_PAIR_GEN,CKM_ECDH1_DERIVE,CKM_ECDSA,CKM_ECDSA_SHA1
  48 sha1:supportedlist=CKM_SHA_1,CKM_SHA_1_HMAC_GENERAL,CKM_SHA_1_HMAC
  49 sha2:supportedlist=CKM_SHA256,CKM_SHA256_HMAC,CKM_SHA256_HMAC_GENERAL,CKM_SHA384,CKM_SHA384_HMAC,CKM_SHA384_HMAC_GENERAL,CKM_SHA512,CKM_SHA512_HMAC,CKM_SHA512_HMAC_GENERAL
  50 md4:supportedlist=CKM_MD4
  51 md5:supportedlist=CKM_MD5,CKM_MD5_HMAC_GENERAL,CKM_MD5_HMAC
  52 rsa:supportedlist=CKM_RSA_PKCS,CKM_RSA_X_509,CKM_MD5_RSA_PKCS,CKM_SHA1_RSA_PKCS,CKM_SHA256_RSA_PKCS,CKM_SHA384_RSA_PKCS,CKM_SHA512_RSA_PKCS
  53 swrand:supportedlist=random
  54 # End SUNWcsr
   1 #
   2 # CDDL HEADER START
   3 #
   4 # The contents of this file are subject to the terms of the
   5 # Common Development and Distribution License (the "License").
   6 # You may not use this file except in compliance with the License.
   7 #
   8 # You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
   9 # or http://www.opensolaris.org/os/licensing.
  10 # See the License for the specific language governing permissions
  11 # and limitations under the License.
  12 #
  13 # When distributing Covered Code, include this CDDL HEADER in each
  14 # file and include the License file at usr/src/OPENSOLARIS.LICENSE.
  15 # If applicable, add the following below this CDDL HEADER, with the
  16 # fields enclosed by brackets "[]" replaced with your own identifying
  17 # information: Portions Copyright [yyyy] [name of copyright owner]
  18 #
  19 # CDDL HEADER END
  20 #
  21 # Copyright 2008 Sun Microsystems, Inc.  All rights reserved.

  22 # Use is subject to license terms.
  23 #


  24 # /etc/crypto/kcf.conf
  25 #
  26 # Do NOT edit this file by hand.   An administrator should use cryptoadm(1m)
  27 # to administer the cryptographic framework.



  28 #
  29 # This document does not constitute an API.  The /etc/crypto/kcf.conf file may
  30 # not exist or may have a different content or interpretation in a future
  31 # release.  The existence of this notice does not imply that any other
  32 # documentation that lacks this notice constitutes an API.
  33 #