Re: tcrypt.ko module usage

[Stephan Mueller <smueller@chronox.de>]

Am Sonntag, 8. März 2015, 14:32:53 schrieb sri sowj:

Hi sri,

> HI All,
> 
> 
> As I understand tcrypt.ko module purpose is to test different crypto
> algorithm from the kenrel space. Please can some one help me with
> below queries to understand tcrypt use cases.
> 
> #1:If one need to test crypto algorithms with under laying crypto
> Hardware engine  using tcrypto module ,is there any method or
> procedure needs to be followed to hook crypto hardware engine with
> tcrypt module?
> 
> As per my understanding its very much straight forward,like if i need
> to test aes algorithm then it will be some thing like  "insmod
> tcrypt.ko mode = 10"

That works if you ensured that your implementation has the highest priority of 
all implementations marked with the cipher names listed in case 10 (as per 
your example):

        case 10:
                ret += tcrypt_test("ecb(aes)");
                ret += tcrypt_test("cbc(aes)");
                ret += tcrypt_test("lrw(aes)");
                ret += tcrypt_test("xts(aes)");
                ret += tcrypt_test("ctr(aes)");
                ret += tcrypt_test("rfc3686(ctr(aes))");
                break;

> 
> #2: Is there any way to test tcrypt module for some scenarios like
>        2.a:concurrency scenario where multiple processes/threads try
> to send a request for same algorithm

This is not implemented with tcrypt. But you can either expand tcrypt, 
implement your own test, test it from user space with the speed test provided 
in [1] or use another implementation of the speed test that may easy be 
expanded [2].

[1] http://www.chronox.de/libkcapi.html
[2] https://www.eperm.de/cryptoperf.html

>        2.b:multiple requests with a same tfm object

dto

>        2.c:back logged message scenarios like multiple methods will be
> sent for processing while crypto engine is serving a request from same
> tfm object

dto
> 
> #3:Is there any significance with
> "CONFIG_CRYPTO_MANAGER_DISABLE_TESTS" Flag? ,Because when I disable
> this flags I observed that tcrypt module
> fails with a message like "Failed to load transform for cbc(aes): -2"

This flag relates to the testmgr.c which implements known answer tests 
executed at the time a cipher implementation is registered.
> 
> 
> BR,
> Srisowj
> --
> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Ciao
Stephan