Hello Herbert
sorry for my pressing ... but I received questions from a distro about if they can pick
this. And the pre requirement is to have this upstream accepted. So will you accept this
and it will appear in the 5.6 kernel or do you want me to do some rework ?
Thanks
On 31.01.20 12:06, Harald Freudenberger wrote:
> On 22.11.19 09:16, Herbert Xu wrote:
>> On Wed, Nov 13, 2019 at 11:55:23AM +0100, Harald Freudenberger wrote:
>>> This patch adds selftests for the s390 specific protected key
>>> AES (PAES) cipher implementations:
>>> * cbc-paes-s390
>>> * ctr-paes-s390
>>> * ecb-paes-s390
>>> * xts-paes-s390
>>> PAES is an AES cipher but with encrypted ('protected') key
>>> material. So here come ordinary AES enciphered data values
>>> but with a special key format understood by the PAES
>>> implementation.
>>>
>>> The testdata definitons and testlist entries are surrounded
>>> by #if IS_ENABLED(CONFIG_CRYPTO_PAES_S390) because they don't
>>> make any sense on non s390 platforms or without the PAES
>>> cipher implementation.
>>>
>>> Signed-off-by: Harald Freudenberger <freude@xxxxxxxxxxxxx>
>>> ---
>>> crypto/testmgr.c | 36 +++++
>>> crypto/testmgr.h | 334 +++++++++++++++++++++++++++++++++++++++++++++++
>>> 2 files changed, 370 insertions(+)
>> So with your cleartext work, I gather that you can now supply
>> arbitrary keys to paes? If so my preferred method of testing it
>> would be to add a paes-specific tester function that massaged the
>> existing aes vectors into the format required by paes so you
>> get exactly the same testing coverage as plain aes.
>>
>> Is this possible?
>>
>> Thanks,
>
> So here is now a reworked version of the paes selftest invocation within the testmanager code.
> I picked your suggestions and now the paes ciphers are able to deal with plain aes key values
> and so can benefit from the generic aes testcases.
> Please note, this patch needs as a prerequirement some other patches which enable the
> base functionality in the zcyrpt device driver and the pkey kernel module. These patches
> will come with the next s390 subsystem merge for the 5.6 development kernel. If you agree
> to this patch, then Vasily will push this patch with the s390 subsystem together as part of the patch
> series.
>
> Thanks and here is the patch for the testmanager:
>
> ============================================================
>
> From fb82ea49910b8cde33ca7286c8855c0326e78177 Mon Sep 17 00:00:00 2001
> From: Harald Freudenberger <freude@xxxxxxxxxxxxx>
> Date: Wed, 22 Jan 2020 14:43:23 +0100
> Subject: [PATCH] crypto/testmgr: enable selftests for paes-s390 ciphers
>
> This patch enables the selftests for the s390 specific protected key
> AES (PAES) cipher implementations:
> * cbc-paes-s390
> * ctr-paes-s390
> * ecb-paes-s390
> * xts-paes-s390
> PAES is an AES cipher but with encrypted ('protected') key
> material. However, the paes ciphers are able to derive an protected
> key from clear key material with the help of the pkey kernel module.
>
> So this patch now enables the generic AES tests for the paes
> ciphers. Under the hood the setkey() functions rearrange the clear key
> values as clear key token and so the pkey kernel module is able to
> provide protected key blobs from the given clear key values. The
> derived protected key blobs are then used within the paes cipers and
> should produce the very same results as the generic AES implementation
> with the clear key values.
>
> The s390-paes cipher testlist entries are surrounded
> by #if IS_ENABLED(CONFIG_CRYPTO_PAES_S390) because they don't
> make any sense on non s390 platforms or without the PAES
> cipher implementation.
>
> Signed-off-by: Harald Freudenberger <freude@xxxxxxxxxxxxx>
> Reviewed-by: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
> Acked-by: Vasily Gorbik <gor@xxxxxxxxxxxxx>
> ---
> crypto/testmgr.c | 36 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
>
> diff --git a/crypto/testmgr.c b/crypto/testmgr.c
> index 82513b6b0abd..6c4a98102825 100644
> --- a/crypto/testmgr.c
> +++ b/crypto/testmgr.c
> @@ -4156,6 +4156,15 @@ static const struct alg_test_desc alg_test_descs[] = {
> .cipher = __VECS(tf_cbc_tv_template)
> },
> }, {
> +#if IS_ENABLED(CONFIG_CRYPTO_PAES_S390)
> + .alg = "cbc-paes-s390",
> + .fips_allowed = 1,
> + .test = alg_test_skcipher,
> + .suite = {
> + .cipher = __VECS(aes_cbc_tv_template)
> + }
> + }, {
> +#endif
> .alg = "cbcmac(aes)",
> .fips_allowed = 1,
> .test = alg_test_hash,
> @@ -4304,6 +4313,15 @@ static const struct alg_test_desc alg_test_descs[] = {
> .cipher = __VECS(tf_ctr_tv_template)
> }
> }, {
> +#if IS_ENABLED(CONFIG_CRYPTO_PAES_S390)
> + .alg = "ctr-paes-s390",
> + .fips_allowed = 1,
> + .test = alg_test_skcipher,
> + .suite = {
> + .cipher = __VECS(aes_ctr_tv_template)
> + }
> + }, {
> +#endif
> .alg = "cts(cbc(aes))",
> .test = alg_test_skcipher,
> .fips_allowed = 1,
> @@ -4596,6 +4614,15 @@ static const struct alg_test_desc alg_test_descs[] = {
> .cipher = __VECS(xtea_tv_template)
> }
> }, {
> +#if IS_ENABLED(CONFIG_CRYPTO_PAES_S390)
> + .alg = "ecb-paes-s390",
> + .fips_allowed = 1,
> + .test = alg_test_skcipher,
> + .suite = {
> + .cipher = __VECS(aes_tv_template)
> + }
> + }, {
> +#endif
> .alg = "ecdh",
> .test = alg_test_kpp,
> .fips_allowed = 1,
> @@ -5167,6 +5194,15 @@ static const struct alg_test_desc alg_test_descs[] = {
> .cipher = __VECS(tf_xts_tv_template)
> }
> }, {
> +#if IS_ENABLED(CONFIG_CRYPTO_PAES_S390)
> + .alg = "xts-paes-s390",
> + .fips_allowed = 1,
> + .test = alg_test_skcipher,
> + .suite = {
> + .cipher = __VECS(aes_xts_tv_template)
> + }
> + }, {
> +#endif
> .alg = "xts4096(paes)",
> .test = alg_test_null,
> .fips_allowed = 1,
