linux-kernel - Re: drivers/char/random.c exported interfaces

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <6.1.1.1.0.20060921162935.01ecb8c0@ptg1.spd.analog.com>
Date:	Thu, 21 Sep 2006 16:35:48 -0400
From:	Robin Getz <rgetz@...ckfin.uclinux.org>
To:	Dave Jones <davej@...hat.com>
Cc:	Dmitry Torokhov <dtor@...ightbb.com>,
	"Randy.Dunlap" <rdunlap@...otime.net>,
	linux-kernel@...r.kernel.org, Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...l.org>
Subject: Re: drivers/char/random.c exported interfaces

Dave Jones pondered:
>Under what circumstances is it desirable to allow INPUT=m ?

I know there are some people using it in their embedded product. I don't 
exactly know _why_, but last time I checked it was to ensure that the 
kernel was as small as possible - which reduces boot time, and their kernel 
flash footprint (kernel and file system are seperate).

The input subsystem is one of the last to be initialized in their system, 
so it allows a little more flexibility in their overall system design.

-Robin 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/