On Tue, 22 Jul 2008, Christopher Ivory 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 mis
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_PKC
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, 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
___
On Tue, 22 Jul 2008, Christopher Ivory wrote:
>When I ran the same test with the pkcs chip initialized ("speed sha1 -engine
>pkcs11") the results were:
>
> The 'numbers' are in 1000s of bytes per second processed.
> type 16 bytes 64 bytes256 bytes 1024 bytes 8192
>b
I think I figured out my problem but I'd like someone to confirm for me that
this seems like a reasonable conclusion. I've been wondering whether or not
I had properly initiated the PKCS11 chip for OpenSSL because I wasn't seeing
much improvement in processing time. I'm trying to sign using the fol
I'm afraid I don't quite follow.
I'm compiling my code with the command lines below:
gcc -Wall -ggdb -DDEBUG LoadDataFromFile.c -c LoadDataFromFile.o
gcc -Wall -ggdb -DDEBUG WriteDataToFile.c -c WriteDataToFile.o
gcc -Wall -ggdb -DDEBUG sign.c -c sign.o
gcc -I /usr/sfw/include -L /usr/
On Tue, 22 Jul 2008, Christopher Ivory wrote:
>Jan,
>
>Thanks for the information! How can I explicitly initialize the PKCS11
>engine when writing in C? I've looked at examples, but I think I'm missing a
>step because when I verify or sign using OpenSSL, I'm seeing no improvement
>in performance.
Jan,
Thanks for the information! How can I explicitly initialize the PKCS11
engine when writing in C? I've looked at examples, but I think I'm missing a
step because when I verify or sign using OpenSSL, I'm seeing no improvement
in performance.
-Chris
On Tue, Jul 22, 2008 at 8:38 AM, Jan Pechane
On Tue, 22 Jul 2008, sadronmeldir wrote:
>I'm aware that the default installation of the Solaris 10 OS provides a
>PKCS#11-based OpenSSL implementation. I'm trying to take some metrics to
>figure out how much more efficient certain processes are with the PKCS
>engine. How would I disable the PKCS
raSPARC T1 processor?
-Chris
--
View this message in context:
http://www.nabble.com/Disabling-the-PKCS--11-on-Solaris-10-tp18587438p18587438.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
__
OpenS
11 matches
Mail list logo
