Dear Stephan, dear Linux folks,
Am 13.07.2017 um 20:20 schrieb Paul Menzel:
Am Mittwoch, den 12.07.2017, 19:38 +0200 schrieb Paul Menzel:
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
Dear Linux crypto folks,
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-bootchar
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
Dear Stephan,
Am Mittwoch, den 12.07.2017, 19:38 +0200 schrieb Paul Menzel:
> 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
Dear Caleb,
Thank you for the report. Linux has a no regression policy, so the
correct forum to report this to is the Linux kernel folks. I am adding
the crypto and stable folks to the receiver list.
Am 26.08.20 um 07:51 schrieb caljor...@hotmail.com:
I wanted to note an issue that I hav
Dear Linux folks,
By mistake I built `XFRM_ESP` into the Linux kernel, resulting in
CONFIG_CRYPTO_SEQIV=y
CONFIG_CRYPTO_ECHAINIV=y
and also the Jitterentropy RNG to be built in.
CRYPTO_JITTERENTROPY=y
So, on the Asus F2A85-M PRO starting Linux 4.10-rc3 with
`initcall_debug`, the
Dear Stephan,
Thank you for the quick reply.
Am 10.11.20 um 10:25 schrieb Stephan Mueller:
Am Montag, 9. November 2020, 20:31:02 CET schrieb Paul Menzel:
By mistake I built `XFRM_ESP` into the Linux kernel, resulting in
CONFIG_CRYPTO_SEQIV=y
CONFIG_CRYPTO_ECHAINIV=y
and also
