Red Hat Bugzilla – Bug 1397547
SSH does not use the ibmca crypto hardware
Last modified: 2017-05-18 07:19:21 EDT
Description of problem: Configured OpenSSL to use ibmca and verified the configuration for Apache but SSHD will not use the modular exponentiation (RSA/DH/DSA) from the crypto adapter. Version-Release number of selected component (if applicable): openssh-5.3p1-118.1.el6_8.s390x openssl-ibmca-1.2.0-4.el6.s390x libica-2.4.2-2.el6.s390x How reproducible: configure the openssl.cnf as described in openssl.cnf.sample-s390x reboot Steps to Reproduce: 1.configure openssl as above 2.reboot 3.run lszcrypt -VVV to check request_count 4.run icastats -r to clear stats 5.open multiple ssh sessions and the counter will not increment 6.run lszcrypt -VVV to check request_count 7.run icastats to verify the software count is incrementing and the hardware count is not Actual results: the request_count will not increment and icastats for hardware will not increment which means that ssh is using the builtin openssl engine instead of offloading to the crypto card Expected results: request_count should increment and icastats should increment for hardware Additional info:
Can you verify it works [1] with current RHEL7.3 (it should)? RHEL6 already reached the maintenance phase and therefore does not accept any new features. But to make sure it is properly evaluated, please contact your Red Hat support [2] (bugzilla is not a support tool). [1] http://bugzilla.redhat.com/1318760 [2] https://www.redhat.com/support/
yes it works with 7.3. this is not a new feature for rhel 6. it used to work in earlier versions of rhel6.
This seems to be related to control master feature introduced some time around RHEL6.5, which is closing all the hanging file descriptors in the processes (unfortunately not noticed during recent updates). We have a patch for RHEL7, which should do the same job also in RHEL6 so please, open your support ticket (with reference to this bugzilla) so I can build you a test package.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2017-0641.html