If it helps, I ran the cryptoadm and got the following results: User-level providers: =====================
Provider: /usr/lib/security/$ISA/pkcs11_kernel.so Mechanisms: CKM_DES_CBC CKM_DES_ECB CKM_DES3_CBC CKM_DES3_ECB CKM_AES_CBC CKM_AES_ECB CKM_RC4 Mechanisms: CKM_DSA CKM_RSA_X_509 CKM_RSA_PKCS Provider: /usr/lib/security/$ISA/pkcs11_softtoken_extra.so Mechanisms: CKM_DES_CBC CKM_DES_CBC_PAD CKM_DES_ECB CKM_DES_KEY_GEN CKM_DES_MAC_GENERAL CKM_DES_MAC CKM_DES3_CBC CKM_DES3_CBC_PAD CKM_DES3_ECB CKM_DES3_KEY_GEN CKM_AES_CBC CKM_AES_CBC_PAD CKM_AES_ECB CKM_AES_KEY_GEN CKM_BLOWFISH_CBC CKM_BLOWFISH_KEY_GEN CKM_SHA_1 CKM_SHA_1_HMAC CKM_SHA_1_HMAC_GENERAL 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 CKM_SSL3_SHA1_MAC CKM_MD5 CKM_MD5_HMAC CKM_MD5_HMAC_GENERAL CKM_SSL3_MD5_MAC CKM_RC4 CKM_RC4_KEY_GEN CKM_DSA CKM_DSA_SHA1 CKM_DSA_KEY_PAIR_GEN CKM_RSA_PKCS CKM_RSA_PKCS_KEY_PAIR_GEN CKM_RSA_X_509 CKM_MD5_RSA_PKCS CKM_SHA1_RSA_PKCS CKM_SHA256_RSA_PKCS CKM_SHA384_RSA_PKCS CKM_SHA512_RSA_PKCS CKM_DH_PKCS_KEY_PAIR_GEN CKM_DH_PKCS_DERIVE CKM_MD5_KEY_DERIVATION CKM_SHA1_KEY_DERIVATION CKM_SHA256_KEY_DERIVATION CKM_SHA384_KEY_DERIVATION CKM_SHA512_KEY_DERIVATION CKM_PBE_SHA1_RC4_128 CKM_PKCS5_PBKD2 CKM_SSL3_PRE_MASTER_KEY_GEN CKM_TLS_PRE_MASTER_KEY_GEN CKM_SSL3_MASTER_KEY_DERIVE CKM_TLS_MASTER_KEY_DERIVE CKM_SSL3_MASTER_KEY_DERIVE_DH CKM_TLS_MASTER_KEY_DERIVE_DH CKM_SSL3_KEY_AND_MAC_DERIVE CKM_TLS_KEY_AND_MAC_DERIVE CKM_TLS_PRF Kernel software providers: ========================== des: CKM_DES_ECB,CKM_DES_CBC,CKM_DES3_ECB,CKM_DES3_CBC aes256: CKM_AES_ECB,CKM_AES_CBC,CKM_AES_CTR arcfour2048: CKM_RC4 blowfish448: CKM_BLOWFISH_ECB,CKM_BLOWFISH_CBC sha1: CKM_SHA_1,CKM_SHA_1_HMAC,CKM_SHA_1_HMAC_GENERAL sha2: 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 md5: CKM_MD5,CKM_MD5_HMAC,CKM_MD5_HMAC_GENERAL rsa: 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 swrand: No mechanisms presented. Kernel hardware providers: ========================== n2cp/0: CKM_DES_CBC,CKM_DES_ECB,CKM_DES3_CBC,CKM_DES3_ECB,CKM_AES_CBC,CKM_AES_ECB,CKM_AES_CTR,CKM_RC4,CKM_MD5,CKM_SHA_1,CKM_SHA256,CKM_MD5_HMAC,CKM_SHA_1_HMAC,CKM_SHA256_HMAC,CKM_MD5_HMAC_GENERAL,CKM_SHA_1_HMAC_GENERAL,CKM_SHA256_HMAC_GENERAL,CKM_SSL3_MD5_MAC,CKM_SSL3_SHA1_MAC ncp/0: CKM_DSA,CKM_RSA_X_509,CKM_RSA_PKCS n2rng/0: No mechanisms presented. On Tue, Jul 22, 2008 at 2:44 PM, Christopher Ivory <[EMAIL PROTECTED]> wrote: > I see what you mean, however, when I get the processor info with the > command "uname -a" it returns: > > SunOS t5200tx 5.10 Generic_120011-14 sun4v sparc > SUNW,SPARC-Enterprise-T5220 > > I was working under the impression that this is a T2. Was I misinformed? > > -Chris > > PS - Thanks for your conitnued help! > > > On Tue, Jul 22, 2008 at 2:22 PM, Jan Pechanec <[EMAIL PROTECTED]> > wrote: > >> On Tue, 22 Jul 2008, Jan Pechanec wrote: >> >> > in OpenSolaris, there is a project that mechanisms that are not >> >implemented in hw will stay in the soft token. >> >> of course, I meant "will stay in OpenSSL" >> >> -- >> Jan Pechanec >> ______________________________________________________________________ >> OpenSSL Project http://www.openssl.org >> User Support Mailing List openssl-users@openssl.org >> Automated List Manager [EMAIL PROTECTED] >> > >
