linux-kernel - Re: Decreasing time for `rsa

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8d89fefa-b27d-ba32-e7b2-75312549ee90@molgen.mpg.de>
Date:   Wed, 12 Jul 2017 19:38:32 +0200
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     Stephan Müller <smueller@...onox.de>
Cc:     linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Decreasing time for `rsa_init`

Dear Stephan,


Thank you for the quick response.


On 07/12/17 19:28, Stephan Müller wrote:
> Am Mittwoch, 12. Juli 2017, 12:59:58 CEST schrieb Paul Menzel:

>> Building CRYPTO_RSA not as module, but into the Linux kernel,
>> `rsa_init()` takes 130 ms on an ASRock E350M1.
>>
>> (Timings are shown by adding `initcall_debug` to Linux command line [1].
>> The times are visualized by `analyze_boot.py` from pm-graph [2] or
>> `systemd-bootchart`.)
>>
>> This is quite a lot of time compared to other modules, and I wonder if
>> there are ways to decrease that time other than building it as a module,
>> and not signing modules?
> 
> Is the testmgr compiled? If yes, the self test may take that time.

It looks like it is, as the tests are not disabled.

```
$ grep MANAGER_DISABLE_TESTS .config
# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
```

I’ll try an image without the tests, and will report back.


Kind regards,

Paul


>> [1] http://elinux.org/Initcall_Debug
>> [2] https://github.com/01org/pm-graph