Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp778174pxj; Thu, 27 May 2021 11:23:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzRpHKf1446sJRn1093lnYTu5gtWOn8HI1ndu5ReQ+UNyxdoxXwMeCTuLTWqyqfyQvMwxo3 X-Received: by 2002:a17:906:b191:: with SMTP id w17mr5342165ejy.200.1622139802487; Thu, 27 May 2021 11:23:22 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1622139802; cv=pass; d=google.com; s=arc-20160816; b=U7kW9ePSVIreIcrhmN26g9w5g/vqKMq0eFiBSvEumy7L925dPRVuOAAf6rW3/FK7P5 Gw5V7LkurbrPXV1UXqnGXTaX7hSa0zB2cQukqNQAddjdhxe7+nvYHQQ+XIB0RNlAO1nh drwU+8FTaCp4cl3T0gfIi6Mm0d3nxQvoU5AHyBMWXc9lZk8gFgYoefbjXhlIxDpqNyhr aCuJI7xHyFyv8A6aT8HwVOrPYqOk3ZXQhqQKfzfMxchV3Ei704pV0EzJ3yRADfQHo0XG Zl6eWETAycTUfaMgS9RhhkJHbqLJRmCclYu6fMY2qQBqE/oAdNR/WaXSFUY00XUxiZL3 oSew== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=NG0bcOYhPORxTimpPLe3u5glAiSJ77lSbbhUollzDgo=; b=T1EN2OBfuflVciSsU5ati+C5VR7jzonpdyIFK3m3b8SM98ryg0K+0BOqiHL1IC7Ld0 l3pNCC7e0GBVv7Ad+LHYBpA0eGfLdKpkqdMu5mVsRdZHWBsHYsZ/Rgy84a5lhrjfVfhU /K1QfatwuKgXkMai0YZSbGxjwhQ/XUmgRcCUwhjTuy1Q/snoNicj6r3BRe1jaTt8fGOR 9i+a4tuZ7yN1CGwFyli1UeJ2MoYu/0DkRIlMqelIG33boMcpWkbfCoi4M50i8G/ubduH yAWl3pWsdlWxqQjNJY//p978EKsrWPCTxZBJ4r/e1OIjsz1An38wJyghqeYbO5hvZepe stTA== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@chronox.de header.s=strato-dkim-0002 header.b=g1ndkVLe; arc=pass (i=1); spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ss11si582715ejb.658.2021.05.27.11.22.58; Thu, 27 May 2021 11:23:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@chronox.de header.s=strato-dkim-0002 header.b=g1ndkVLe; arc=pass (i=1); spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237216AbhE0QOv (ORCPT + 99 others); Thu, 27 May 2021 12:14:51 -0400 Received: from mo4-p04-ob.smtp.rzone.de ([81.169.146.176]:35091 "EHLO mo4-p04-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237172AbhE0QO2 (ORCPT ); Thu, 27 May 2021 12:14:28 -0400 ARC-Seal: i=1; a=rsa-sha256; t=1622131897; cv=none; d=strato.com; s=strato-dkim-0002; b=rnrIK+sd9kSUsGNG82bhpAJkzzePu1czMZwqMJU91G//DoJaBmzgN2hN63oKpf2vgc 767OL56ih+Vly3tWSD4IQ9TG2Nj1UwkfhYfbgyxIDEgZi+LKh2lcpX+qdZke3hh5ZDCu PT7v679dNHVQsY6dMEhJ1TUM4/ia8ewZFl11Q9I59ElhocmiSOvdZXAkGOvVAfITMX2n MGtM1031Hu4xFXBq6NwJnfzdyWma012kb5q5eJYHzX1M+ye2IkcZlw0RT3wrGkhH25p/ 82a3VJCV2SxuFDAHsxkF7Yw/gmeq9YG7Ex4nw6BPe4WgihBrvJC3OrP6jLLwseM2Q35Y V8IQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; t=1622131897; s=strato-dkim-0002; d=strato.com; h=Message-ID:Date:Subject:Cc:To:From:Cc:Date:From:Subject:Sender; bh=NG0bcOYhPORxTimpPLe3u5glAiSJ77lSbbhUollzDgo=; b=QPTOYH7qpLeo50KfbisoeTSZ+SbGbzGMcvjg4gfIY0LtZEESfyQWCKX1h3n56HPpgn zEdPgB/af2Kdx3T7dJdKWG3TkRpJr22YtIaP3H+cYsriMb79jkN/7xK1bvJQBGdkwwmo UeOf49NlfuSQU6+/keqdkjcS4ejIaqqjSe0uyVEO+bkKMAWPFTJUqKYbIb/UJnNyS01B 0mmWXzyl3AyeNAovbnVDmyk6Sst0uaQKCpvQsREqvImf+kNwrncWNKwJxIl3Y2NoNBNj 50ayKcWosj2eJUnohYTXSF/1hkQZVMckuUDSYvSWLwZPtwD72g3sBlBtB63Q55gjS/6u JJ6A== ARC-Authentication-Results: i=1; strato.com; dkim=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1622131897; s=strato-dkim-0002; d=chronox.de; h=Message-ID:Date:Subject:Cc:To:From:Cc:Date:From:Subject:Sender; bh=NG0bcOYhPORxTimpPLe3u5glAiSJ77lSbbhUollzDgo=; b=g1ndkVLe/k3wIAY67elYav5uJiJEZE6a0xai68f5mMzxuCtTYQjwC/ChO8aDb8zFaA cUgVGYlJPkVQH5tOw8Jo945vmR0lCmU1v2NnSjbPzei5N3qAQPsS/4tVBM1iBf1IofcK NtVv4+WE9QiBaKNKTXQwFNcGyE3Yk2A0mLDprB2hGgREDstj6i6TLxUi0+uHCQrjyYnf 6tkiSh72MMVMhBS0dOjsT+Ji6wf3xS0Ap1ugsgIc8Xj82g1gIYbuQiSFMErc9hgm1q06 9EsXBOhEpuL8MaSHnPJKMW2FVwenJFnJ7ww16ADqljySLzj8cp/7BuDbUNfuEBYOQ3d+ 4mZw== Authentication-Results: strato.com; dkim=none X-RZG-AUTH: ":P2ERcEykfu11Y98lp/T7+hdri+uKZK8TKWEqNyiHySGSa9k9xmwdNnzGHXPbJvSfFeK2" X-RZG-CLASS-ID: mo00 Received: from positron.chronox.de by smtp.strato.de (RZmta 47.26.3 DYNA|AUTH) with ESMTPSA id R0123ax4RGBa0Tx (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Thu, 27 May 2021 18:11:36 +0200 (CEST) From: Stephan =?ISO-8859-1?Q?M=FCller?= To: Tso Ted , linux-crypto@vger.kernel.org Cc: Willy Tarreau , Nicolai Stange , LKML , Arnd Bergmann , Greg Kroah-Hartman , "Eric W. Biederman" , "Alexander E. Patrakov" , "Ahmed S. Darwish" , Matthew Garrett , Vito Caputo , Andreas Dilger , Jan Kara , Ray Strode , William Jon McCann , zhangjs , Andy Lutomirski , Florian Weimer , Lennart Poettering , Peter Matthias , Marcelo Henrique Cerri , Neil Horman , Randy Dunlap , Julia Lawall , Dan Carpenter , Andy Lavr , Eric Biggers , "Jason A. Donenfeld" , Petr Tesarik , John Haxby Subject: [PATCH v40 00/13] /dev/random - a new approach Date: Thu, 27 May 2021 17:53:00 +0200 Message-ID: <18450229.rjpLZT9oXI@positron.chronox.de> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Hi, The following patch set provides a different approach to /dev/random which is called Linux Random Number Generator (LRNG) to collect entropy within the Linux kernel. It provides the same API and ABI and can be used as a drop-in replacement. The LRNG implements at least all features of the existing /dev/random such = as NUMA-node-local DRNGs. Patches 1 through 3 provide the code that is feature- identical. The following advantages compared to the existing /dev/random implementation are present: * Sole use of crypto for data processing: - Exclusive use of a hash operation for conditioning entropy data with a clear mathematical description as given in [2] section 2.2 - non-cryptographic operations like LFSR are not used. - The LRNG uses only properly defined and implemented cryptographic algorithms unlike the use of the SHA-1 transformation in the existing /dev/random implementation. - Hash operations use NUMA-node-local hash instances to benefit large parallel systems. - LRNG uses limited number of data post-processing steps as documented in [2] section 2.2 compared to the large variation of different post-processing steps in the existing /dev/random implementation that have no apparent mathematical description (see [2] section 4.5). * Performance - Faster by up to 130% in the critical code path of the interrupt handler depending on data collection size configurable at kernel compile time - the default is now set such that the highest performance is achieved as outlined in [2] section 4.2. - Configurable data collection sizes to accommodate small environments and big environments via CONFIG_LRNG_COLLECTION_SIZE. - Entropy collection using an almost never contended lock to benefit large parallel systems =E2=80=93 worst case rate of contention is the nu= mber of DRNG reseeds, usually the number of potential contentions per 10 minutes is equal to number of NUMA nodes. - ChaCha20 DRNG is significantly faster as implemented in the existing /dev/random as demonstrated with [2] table 2. - Faster entropy collection during boot time to reach fully seeded level, including on virtual systems or systems with SSDs as outlined in [2] section 4.1. * Testing - Availability of run-time health tests of the raw unconditioned noise source to identify degradation of the available entropy as documented in [2] section 2.5.4. Such health tests are important today due to virtual machine monitors reducing the resolution of or disabling the high-resolution timer. - Heuristic entropy estimation is based on quantitative measurements and analysis following SP800-90B and not on coincidental underestimation of entropy applied by the existing /dev/random as outlined in [4] section 4.4. - Power-on self tests for critical deterministic components (ChaCha20 DRNG, software hash implementation, and entropy collection logic) not already covered by power-up tests of the kernel crypto API as documented in [2] section 2.14. - Availability of test interfaces for all operational stages of the LRNG including boot-time raw entropy event data sampling as outlined in [2] section 2.15. - Fully testable ChaCha20 DRNG via a userspace ChaCha20 DRNG implementation [3]. - In case of using the kernel crypto API SHASH hash implementation, it is fully testable and tested via the NIST ACVP test framework, for example certificates A734, A737, and A738. - The LRNG offers a test interface to validate the used software hash implementation and in particular that the LRNG invokes the hash correctly, allowing a NIST ACVP-compliant test cycle - see [2] section 2.15. - Availability of stress testing covering the different code paths for data and mechanism (de)allocations and code paths covered with locks. * Entropy collection - The LRNG is shipped with test tools allowing the collection of raw unconditioned entropy during runtime and boot time available at [1]. - Full entropy assessment and description is provided with [2] chapter 3, specifically section 3.2.6. - Guarantee that entropy events are not credited with entropy twice (the existing /dev/random implementation credits HID/disk and interrupt events with entropy which are a derivative of each other). * Configurable - LRNG kernel configuration allows configuration that is functionally equivalent to the existing /dev/random. Non-compiled additional code is folded into no-ops. - The following additional functions are compile-time selectable independent of each other: + Enabling of switchable cryptographic implementation support. This allows enabling an SP800-90A DRBG. + Enabling of using Jitter RNG noise source. + Enabling of noise source health tests. + Enabling of test interface allowing to enable each test interface individually. + Enabling of the power-up self test. - At boot-time, the SP800-90B health tests can be enabled as outlined in [2] section 2.5.4. - At boot-time, the entropy rate used to credit the external CPU-based noise source and Jitter RNG noise source can be configured including setting an entropy rate of zero or full entropy - see [2] sections 2.5.2 and 2.5.3. * Run-time pluggable cryptographic implementations used for all data processing steps specified in [2] section 2.2 - The DRNG can be replaced with a different implementation allowing any type of DRNG to provide data via the output interfaces. The LRNG provides the following types of DRNG implementations: + ChaCha20-based software implementation that is used per default. + SP800-90A DRBG using accelerated cryptographic implementations that may sleep. + Any DRNG that is accessible via the kernel crypto API RNG subsystem. - The hash component can be replaced with any other hash implementation provided the implementation does not sleep. The LRNG provides the access to the following types of non-sleeping hash implementations: + SHA-256 software implementation that is used per default. Due to kernel build system inconsistencies, the software SHA-1 implementation is used if the kernel crypto API is not compiled. + SHA-512 hash using the fastest hash implementation available via the kernel crypto API SHASH subsystem. * Code structure - The LRNG source code is available for current upstream Linux kernel separate to the existing /dev/random which means that users who are conservative can use the unchanged existing /dev/random implementation. - Back-port patches are available at [5] to apply the LRNG to Linux kernel versions of 5.8, 5.4, 4.19, 4.14, 4.12, 4.10, and 4.4. Patches for other kernel versions are easily derived from the existing ones. Booting the patch with the kernel command line option "dyndbg=3Dfile drivers/char/lrng/* +p" generates logs indicating the operation of the LRNG. Each log is pre-pended with "lrng". An entropy analysis is performed on the following systems - details are given in [2] appendix C: * x86 KVM virtualized guest 32 and 64 bit systems * x86 bare metal * older and newer ARMv7 system * ARM64 * POWER7 LE and POWER 8 BE * IBM Z System mainframe * old MIPS embedded device * testing with GCC and Clang [1] https://www.chronox.de/lrng.html - If the patch is accepted, I would be volunteering to convert the documentation into RST format and contribute it to the Linux kernel documentation directory. [2] https://www.chronox.de/lrng/doc/lrng.pdf [3] https://www.chronox.de/chacha20_drng.html [4] https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/Studie= s/LinuxRNG/LinuxRNG_EN_V4_1.pdf [5] https://github.com/smuellerDD/lrng/tree/master/backports Changes (compared to the previous patch set) - individual patches are visible at https://github.com/smuellerDD/lrng/commits/master: =2D add dependency to CRYPTO_HASH when compiling lrng_kcapi_hash =2D initialize Jitter RNG during device_initcall =2D speed up early boot entropy gathering =2D add sha1.h include in case the kernel crypto API is not compiled CC: Torsten Duwe CC: "Eric W. Biederman" CC: "Alexander E. Patrakov" CC: "Ahmed S. Darwish" CC: "Theodore Y. Ts'o" CC: Willy Tarreau CC: Matthew Garrett CC: Vito Caputo CC: Andreas Dilger CC: Jan Kara CC: Ray Strode CC: William Jon McCann CC: zhangjs CC: Andy Lutomirski CC: Florian Weimer CC: Lennart Poettering CC: Nicolai Stange CC: Eric Biggers Tested-by: Marcelo Henrique Cerri Stephan Mueller (13): Linux Random Number Generator LRNG - allocate one DRNG instance per NUMA node LRNG - sysctls and /proc interface LRNG - add switchable DRNG support LRNG - add common generic hash support crypto: DRBG - externalize DRBG functions for LRNG LRNG - add SP800-90A DRBG extension LRNG - add kernel crypto API PRNG extension crypto: provide access to a static Jitter RNG state LRNG - add Jitter RNG fast noise source LRNG - add SP800-90B compliant health tests LRNG - add interface for gathering of raw entropy LRNG - add power-on and runtime self-tests MAINTAINERS | 7 + crypto/drbg.c | 16 +- crypto/jitterentropy-kcapi.c | 3 +- crypto/jitterentropy.c | 31 +- drivers/char/Kconfig | 2 + drivers/char/Makefile | 9 +- drivers/char/lrng/Kconfig | 443 +++++++++++ drivers/char/lrng/Makefile | 20 + drivers/char/lrng/lrng_archrandom.c | 94 +++ drivers/char/lrng/lrng_aux.c | 136 ++++ drivers/char/lrng/lrng_chacha20.c | 320 ++++++++ drivers/char/lrng/lrng_chacha20.h | 29 + drivers/char/lrng/lrng_drbg.c | 198 +++++ drivers/char/lrng/lrng_drng.c | 428 +++++++++++ drivers/char/lrng/lrng_health.c | 410 +++++++++++ drivers/char/lrng/lrng_interfaces.c | 649 +++++++++++++++++ drivers/char/lrng/lrng_internal.h | 452 ++++++++++++ drivers/char/lrng/lrng_jent.c | 91 +++ drivers/char/lrng/lrng_kcapi.c | 227 ++++++ drivers/char/lrng/lrng_kcapi_hash.c | 103 +++ drivers/char/lrng/lrng_kcapi_hash.h | 20 + drivers/char/lrng/lrng_numa.c | 120 +++ drivers/char/lrng/lrng_pool.c | 563 ++++++++++++++ drivers/char/lrng/lrng_proc.c | 186 +++++ drivers/char/lrng/lrng_selftest.c | 351 +++++++++ drivers/char/lrng/lrng_sw_noise.c | 649 +++++++++++++++++ drivers/char/lrng/lrng_sw_noise.h | 71 ++ drivers/char/lrng/lrng_switch.c | 219 ++++++ drivers/char/lrng/lrng_testing.c | 689 ++++++++++++++++++ include/crypto/drbg.h | 7 + .../crypto/internal}/jitterentropy.h | 3 + include/linux/lrng.h | 81 ++ 32 files changed, 6617 insertions(+), 10 deletions(-) create mode 100644 drivers/char/lrng/Kconfig create mode 100644 drivers/char/lrng/Makefile create mode 100644 drivers/char/lrng/lrng_archrandom.c create mode 100644 drivers/char/lrng/lrng_aux.c create mode 100644 drivers/char/lrng/lrng_chacha20.c create mode 100644 drivers/char/lrng/lrng_chacha20.h create mode 100644 drivers/char/lrng/lrng_drbg.c create mode 100644 drivers/char/lrng/lrng_drng.c create mode 100644 drivers/char/lrng/lrng_health.c create mode 100644 drivers/char/lrng/lrng_interfaces.c create mode 100644 drivers/char/lrng/lrng_internal.h create mode 100644 drivers/char/lrng/lrng_jent.c create mode 100644 drivers/char/lrng/lrng_kcapi.c create mode 100644 drivers/char/lrng/lrng_kcapi_hash.c create mode 100644 drivers/char/lrng/lrng_kcapi_hash.h create mode 100644 drivers/char/lrng/lrng_numa.c create mode 100644 drivers/char/lrng/lrng_pool.c create mode 100644 drivers/char/lrng/lrng_proc.c create mode 100644 drivers/char/lrng/lrng_selftest.c create mode 100644 drivers/char/lrng/lrng_sw_noise.c create mode 100644 drivers/char/lrng/lrng_sw_noise.h create mode 100644 drivers/char/lrng/lrng_switch.c create mode 100644 drivers/char/lrng/lrng_testing.c rename {crypto =3D> include/crypto/internal}/jitterentropy.h (84%) create mode 100644 include/linux/lrng.h =2D-=20 2.31.1