linux-kernel - [PATCH 0/3] No longer default to HW_RANDOM when UML

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-next>] [day] [month] [year] [list]

Message-Id: <cover.1736946020.git.dsimic@manjaro.org>
Date: Wed, 15 Jan 2025 14:06:59 +0100
From: Dragan Simic <dsimic@...jaro.org>
To: linux-crypto@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
	olivia@...enic.com,
	herbert@...dor.apana.org.au,
	didi.debian@...ow.org,
	heiko@...ech.de,
	dsimic@...jaro.org
Subject: [PATCH 0/3] No longer default to HW_RANDOM when UML_RANDOM is the trigger

This is a small patch series that makes the already existing HW_RANDOM_*
options in the hw_random Kconfig selected by default only when the
UML_RANDOM option isn't already selected.  Having the HW_RANDOM_* options
selected doesn't make much sense for user-mode Linux (UML), which obviously
cannot make use of any HWRNG devices.

Along the way, some additional trivial cleanups of the hw_random Kconfig
file are also performed as spotted, in separate patches.

Dragan Simic (3):
  hwrng: Use tabs as leading whitespace consistently in Kconfig
  hwrng: Move one "tristate" Kconfig description to the usual place
  hwrng: Don't default to HW_RANDOM when UML_RANDOM is the trigger

 drivers/char/hw_random/Kconfig | 84 +++++++++++++++++-----------------
 1 file changed, 42 insertions(+), 42 deletions(-)