On 2/15/11 10:19 AM, Rogério Soares wrote:
> 
> but, i shoud be able to see some increase on Per-device successfully
> completed request counts ?
> 
> Thanks for you attention :)
> 
Yes, they do increase for me each time I login via ssh:

pzsadm01:~ # cat /proc/driver/z90crypt

zcrypt version: 2.1.1
Cryptographic domain: 9
Total device count: 1
PCICA count: 0
PCICC count: 0
PCIXCC MCL2 count: 0
PCIXCC MCL3 count: 0
CEX2C count: 0
CEX2A count: 1
requestq count: 0
pendingq count: 0
Total open handles: 2


Online devices: 1=PCICA 2=PCICC 3=PCIXCC(MCL2) 4=PCIXCC(MCL3) 5=CEX2C 6=CEX2A
           0000000000000000 0000000000000000 6000000000000000 0000000000000000


Waiting work element counts
           0000000000000000 0000000000000000 0000000000000000 0000000000000000


Per-device successfully completed request counts
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000009 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 

Here's what I have installed:

libica-1.3.8-0.7
libica-32bit-1.3.8-0.7
openCryptoki-2.2.4-0.12.10
openCryptoki-32bit-2.2.4-0.12.10
openCryptoki-64bit-2.2.4-0.12.10
openssh-4.2p1-18.40.35  <-- has been modified with the extra define
openssl-0.9.8a-18.42.2
openssl-32bit-0.9.8a-18.42.2
openssl-ibmca-1.0.0-7.16
openssl-ibmca-32bit-1.0.0-7.16 

Here's what I get when querying crypto support from with a guest:

pzsadm01:~ # vmcp q crypto ap
AP 00 CEX2C Queue 12 is superseded by CEX2A
AP 01 CEX2A Queue 12 is installed
AP 02 CEX2C Queue 12 is superseded by CEX2A
AP 03 CEX2A Queue 12 is installed

Here's what my openssl.cnf file looks like.  One thing that I recall running 
into was the correct placement of the openssl_cnf line.  Make sure it comes 
before the [new_oids] section.

#
# OpenSSL example configuration file.
# This is mostly being used for generation of certificate requests.
#
# This definition stops the following lines choking if HOME isn't
# defined.
HOME                    = .
RANDFILE                = $ENV::HOME/.rnd

# Extra OBJECT IDENTIFIER info:
#oid_file               = $ENV::HOME/.oid
oid_section             = new_oids

openssl_conf = openssl_def

# To use this configuration file with the "-extfile" option of the
# "openssl x509" utility, name here the section containing the
# X.509v3 extensions to use:
# extensions            =
# (Alternatively, use a configuration file that has only
# X.509v3 extensions in its main [= default] section.) 

<<<snip>>>

[openssl_def]
engines = engine_section

[engine_section]
foo = ibmca_section

[ibmca_section]
dynamic_path = /usr/lib64/engines/libibmca.so
engine_id = ibmca
default_algorithms = ALL
#default_algorithms = RAND,RSA
init = 1 

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to