path: root/wpa_supplicant/defconfig
diff options
authorLubomir Rintel <lkundrak@v3.sk>2017-09-18 12:58:07 (GMT)
committerJouni Malinen <j@w1.fi>2019-01-01 23:24:18 (GMT)
commit89a7cdd690b48a0c56380cf4609442ed13527f44 (patch)
treea4c9f2c6c66bb6429bf4122f7ad0fbcf68000db9 /wpa_supplicant/defconfig
parent2a54979695597f362bd5cfcccb77dfb99b61ed9e (diff)
crypto: Add option to use getrandom()
According to random(4) manual, /dev/random is essentially deprecated on Linux for quite some time: "The /dev/random interface is considered a legacy interface, and /dev/urandom is preferred and sufficient in all use cases, with the exception of applications which require randomness during early boot time; for these applications, getrandom(2) must be used instead, because it will block until the entropy pool is initialized." An attempt to use it would cause unnecessary blocking on machines without a good hwrng even when it shouldn't be needed. Since Linux 3.17, a getrandom(2) call is available that will block only until the randomness pool has been seeded. It is probably not a good default yet as it requires a fairly recent kernel and glibc (3.17 and 2.25 respectively). Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
Diffstat (limited to 'wpa_supplicant/defconfig')
1 files changed, 5 insertions, 0 deletions
diff --git a/wpa_supplicant/defconfig b/wpa_supplicant/defconfig
index da0b3f1..0a08252 100644
--- a/wpa_supplicant/defconfig
+++ b/wpa_supplicant/defconfig
@@ -461,6 +461,11 @@ CONFIG_BACKEND=file
# that meet the requirements described above.
+# Should we attempt to use the getrandom(2) call that provides more reliable
+# yet secure randomness source than /dev/random on Linux 3.17 and newer.
+# Requires glibc 2.25 to build, falls back to /dev/random if unavailable.
# IEEE 802.11n (High Throughput) support (mainly for AP mode)