I did a local build incl. test runs and got the following results:
============================================================================
Testsuite summary for openssl-ibmca 2.2.1
============================================================================
# TOTAL: 34
# PASS: 27
# SKIP: 2
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 5
============================================================================
See test/test-suite.log
Please report to <email address hidden>
I checked these results with upstream and got the information that:
1) the des and 3des errors are known with openssl 3.0
the config should load the legacy provider here,
since openssl 3 sees des and 3des as deprecated
and moved it to the legacy-provider
2) the fact that loadtest and threadtest got skipped is due to our outdated (crypto) hardware
So this is expected (and similar to a test run with the previous version 2.2.0).
I did a local build incl. test runs and got the following results: ======= ======= ======= ======= ======= ======= ======= ======= ======= ====== ======= ======= ======= ======= ======= ======= ======= ======= ======= ====== ======= ======= ======= ======= ======= ======= ======= ======= ======= ======
=======
Testsuite summary for openssl-ibmca 2.2.1
=======
# TOTAL: 34
# PASS: 27
# SKIP: 2
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 5
=======
See test/test-suite.log
Please report to <email address hidden>
I checked these results with upstream and got the information that:
1) the des and 3des errors are known with openssl 3.0
the config should load the legacy provider here,
since openssl 3 sees des and 3des as deprecated
and moved it to the legacy-provider
2) the fact that loadtest and threadtest got skipped is due to our outdated (crypto) hardware
So this is expected (and similar to a test run with the previous version 2.2.0).