Am Samstag, 16. September 2017, 15:00:34 CEST schrieb Jason A. Donenfeld: Hi Jason, > This started out as just replacing the use of crypto/rng with > get_random_bytes_wait, This change is a challenge. The use of the kernel crypto API's DRNG has been made to allow FIPS 140-2 compliance. Otherwise, the entire key generation logic will not be using the right(TM) DRNG. Thus, I would not suggest to replace that for a stable tree. Note, I am currently working on a pluggable DRNG apporach for /dev/random and /dev/urandom to be able to get rid of the use of the kernel crypto API's DRNG API. It is ready and I will air that solution shortly. Yet, it needs work to be integrated upstream (and approval from Ted Tso). Ciao Stephan