And what Steve thought about adding another step to the test plan that does a 'zkey generate --key-type EP11` (so for the traditional type), but the zkey gen command only support secure keys of type CCA‐AESDATA keys, CCA‐AESCIPHER and EP11‐AES (so no EP11-ECC for suchlike).
Instead I'm wondering if it makes sense to generate a zkey on such a newer system (means with this updated s390-tools version and the right kernel), but doing a validate on an older system (without these patches), like for example on 22.04.
Would that be a meaningful regression test case?
Please notice that the comment numbering between Launchpad and Bugzilla is not in sync. /bugs.launchpad .net/ubuntu/ +source/ s390-tools/ +bug/2028936/ comments/ 4
I guess Ingo refers to Launchpad comment #2:
https:/
with the zkey generate and validate commands.
And what Steve thought about adding another step to the test plan that does a 'zkey generate --key-type EP11` (so for the traditional type), but the zkey gen command only support secure keys of type CCA‐AESDATA keys, CCA‐AESCIPHER and EP11‐AES (so no EP11-ECC for suchlike).
Instead I'm wondering if it makes sense to generate a zkey on such a newer system (means with this updated s390-tools version and the right kernel), but doing a validate on an older system (without these patches), like for example on 22.04.
Would that be a meaningful regression test case?