On Tue, Nov 12, 2013 at 06:53:50AM -0500, Theodore Ts'o wrote: > > Btw. do you see problems regarding get_random_int on architectures without > > hardware offloading? > > > > We are initializing random_int_secret really late (after all the init > > calls) and I wonder if we should also use a two stage initialization > > there, so we have a more unpredictable MD5 hash at early boot. > > Most of the users of get_random_int(), at least to date, have been for > things like ASLR. A quick audit shows only one device driver user > that might be impacted: drivers/net/wireless/cw1200/wsm.c. > > It's not a bad idea to do a two stage init just in case > get_random_int() gets used by other code --- although that brings up > something that I know is really needed, but which I haven't had time > to try to address yet: we really need to document all of the various > interfaces that various kernel routines can use to get random numbers, > and document what their performance and security characteristics are. > We have probably have a lot of code where the authors didn't realize > that some other interface would be a better match for their needs, or > the code is old enough that predates some of the newer interfaces. It is needed by fork to set up the stack canary. And this actually gets called before the secret is initialized. Btw. the kaslr seeding techniques become quite interesting. It looks like they want to hash struct boot_params, maybe the ACPI memory part and also the DMI table. I guess we should start to implement an interface for early-boot entropy which the architectures must override to not use jiffies ^ get_cycles() all the time. The documentation idea also does sound as a very good one. ;) Greetings, Hannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
