Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1668638
| From | Stephan Müller <smueller@chronox.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [kernel-hardening] Re: [PATCH v4 13/13] random: warn when kernel uses unseeded randomness |
| Date | 2017-06-18 20:00 +0200 |
| Message-ID | <tTMEp-8ff-3@gated-at.bofh.it> (permalink) |
| References | <tPqM9-3tE-3@gated-at.bofh.it> <tSBBn-210-7@gated-at.bofh.it> <tTKCB-6Ye-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Am Sonntag, 18. Juni 2017, 17:46:25 CEST schrieb Theodore Ts'o: Hi Theodore, > > IMHO, users using the get_random_u64 or get_random_u32 are use cases that > > do not require a fully seeded DRNG thus do not need a cryptographically > > strong random number. Hence, I would think that the logging should be > > removed from get_random_u32/u64. > > You are effectively proposing that there ought to be a middle range of > security between prandom_32, get_random_u32/get_random_u64 and > get_random_bytes(). I think that's going to lead to all sorts of > complexity and bugs from people not understanding when they should use > get_random_u32 vs get_random_bytes versus prandom_u32. And then we'll > end up needing to audit all of the callsites for get_random_u32() so > they don't violate this new usage rule that you are proposing. I only proposed to get rid of the log messages indicating a non-seeded DRNG. But you bring up an interesting point: if it is true you say that it is hard for people to use differnent types of APIs regarding entropy and random numbers right (which I would concur with), and considering that you imply that get_random_bytes, get_random_u32 and get_random_u64 have the same security strength, why do we have these three APIs to begin with? The get_random_bytes API would then be more than enough. Ciao Stephan
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH v4 13/13] random: warn when kernel uses unseeded randomness Theodore Ts'o <tytso@mit.edu> - 2017-06-08 10:20 +0200
Re: [PATCH v4 13/13] random: warn when kernel uses unseeded randomness "Jason A. Donenfeld" <Jason@zx2c4.com> - 2017-06-08 14:10 +0200
Re: [kernel-hardening] Re: [PATCH v4 13/13] random: warn when kernel uses unseeded randomness Michael Ellerman <mpe@ellerman.id.au> - 2017-06-15 13:10 +0200
Re: [kernel-hardening] Re: [PATCH v4 13/13] random: warn when kernel uses unseeded randomness Stephan Müller <smueller@chronox.de> - 2017-06-15 14:00 +0200
Re: [kernel-hardening] Re: [PATCH v4 13/13] random: warn when kernel uses unseeded randomness Theodore Ts'o <tytso@mit.edu> - 2017-06-18 17:50 +0200
Re: [kernel-hardening] Re: [PATCH v4 13/13] random: warn when kernel uses unseeded randomness Stephan Müller <smueller@chronox.de> - 2017-06-18 20:00 +0200
Re: [kernel-hardening] Re: [PATCH v4 13/13] random: warn when kernel uses unseeded randomness "Jason A. Donenfeld" <Jason@zx2c4.com> - 2017-06-18 21:20 +0200
Re: [kernel-hardening] Re: [PATCH v4 13/13] random: warn when kernel uses unseeded randomness "Jason A. Donenfeld" <Jason@zx2c4.com> - 2017-06-18 21:20 +0200
csiph-web