I've noticed that v2.2.3 is obviously a bugfix-only release:
...
93a12d3 (tag: v2.2.3) Update to version 2.2.3
6563dd2 use correct libica for ibmca_mechaList_test
e91e179 PKEY: Fix usage of ECX keys
fae4490 (tag: v2.2.2) Update to version 2.2.2
...
and according to the FFe definition, bugfix-only updates might be acceptable,
so I will follow that route.
I've created such a package:
openssl-ibmca (2.2.3-0ubuntu1) jammy; urgency=medium
* New upstream release. LP: #1967141
* The difference between 2.2.2 and 2.2.3 includes just these two fixes:
- "PKEY: Fix usage of ECX keys"
- "use correct libica for ibmca_mechaList_test"
Rather than adding these as quilt patches, raising the package to the
bugfix-only version that incl. them is preferable.
* For "PKEY: Fix usage of ECX keys" a backport of
"Fix compilation for OpenSSL 3.0" was needed:
d/p/e59cce5-Fix-compilation-for-OpenSSL-3.0.patch
* For convenience reasons a generated sample config is now included in
the package, but also the optional configuration generator Perl script
'ibmca-engine-opensslconfig'.
It built fine locally (on s390x - it's an s390x-only package).
In addition I've did a PPA build of this package which is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1967141
The build includes a run of the test suite:
local build:
============================================================================
Testsuite summary for openssl-ibmca 2.2.3
============================================================================
# TOTAL: 34
# PASS: 28
# SKIP: 6
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
PPA:
============================================================================
Testsuite summary for openssl-ibmca 2.2.3
============================================================================
# TOTAL: 34
# PASS: 26
# SKIP: 8
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
(Two more tests are (auto-)skipped, because the builder does not have access to
the s390x crypto hardware.
(The other skipped tests are skipped by upstream, since they are known to cause
issues on openssl 3 systems).
On top I installed, tested ad verified the package on an s390x system:
$ uname -a
Linux s1lp15 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:53:58 UTC 2022
s390x s390x s390x GNU/Linux
$ apt-cache policy openssl-ibmca
openssl-ibmca:
Installed: 2.2.3-0ubuntu1
Candidate: 2.2.3-0ubuntu1
Version table:
*** 2.2.3-0ubuntu1 100
100 /var/lib/dpkg/status
2.2.2-0ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports jammy/universe s390x Packages
And I can confirm that sshd does NOT core dump.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967141
Title:
[UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps
core (openssl-ibmca)
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
---Problem Description---
Summary
=======
New IBM HW with Crypto Accelerator cards attached
Kernel level: 5.14
Core dump when configuring the ibmca engine with libica = libica.so.4 in the
openssl.cnf file in the engine section.
The problem only occurs with OpenSSL 3.0 and is immediately reproducible.
Details
=======
HINT: To be able to receive core dump files at all it is needed to change the
/etc/systemd/system.conf file entry DefaultLimitCORE=0:infinity to read
DefaultLimitCORE=infinity:infinity
On a system with ibmca engine configured system wide, when trying to
use the libica.so.4 to support the ibmca engine the sshd daemon dumps
core upon the first login attempt.
# openssl engine -c
(dynamic) Dynamic engine loading support
(ibmca) Ibmca hardware engine support
[RSA, DSA, DH]
Debug Data
==========
core dump file in the attachments.
Contact Information = [email protected]
---uname output---
Linux system 5.14.
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1.) Edit /etc/systemd/system.conf file to allow core dumps:
Change the line DefaultLimitCORE=0:infinity
to read DefaultLimitCORE=infinity:infinity
2.) run: systemctl daemon-reload
systemctl restart systemd-coredump.socket
3.) Run the /usr/share/doc/openssl-ibmca/ibmca-engine-opensslconfig perl
script
4.) Edit the /etc/pki/tls file near the end to contain the line
to back the ibmca engine by the libica.so.4 library as outlined in the
/usr/share/doc/openssl-ibmca/README.md file
5.) Run: openssl engine -c
6.) Keep the current session open for subsequently stepping back to the
original openssl.cnf!
7.) Open up a new ssh session to the system under test
and watch the login to fail with broken pipe
8.) On the remaining session, run
coreumpctl list / coredumpctl dump
Userspace tool common name: openssl-ibmca
Userspace rpm: openssl-ibmca-2.2.2-1.el9.s390x
The userspace tool has the following bit modes: 64bit
Userspace tool obtained from project website: na
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1967141/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
