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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20060921191551.GC17065@redhat.com>
Date:	Thu, 21 Sep 2006 15:15:51 -0400
From:	Dave Jones <davej@...hat.com>
To:	Dmitry Torokhov <dtor@...ightbb.com>
Cc:	Robin Getz <rgetz@...ckfin.uclinux.org>,
	"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

On Thu, Sep 21, 2006 at 12:11:25AM -0400, Dmitry Torokhov wrote:
 > On Wednesday 20 September 2006 13:04, Robin Getz wrote:
 > > Randy Dunlap said:
 > > >ISTM that we should at least fix the first 2 (by EXPORTing them).
 > > >or we don't allow INPUT=m.
 > > >
 > > >You want to send a patch?
 > > 
 > > No problem - which patch do you want? (exporting? or set INPUT to bool?)
 > > 
 > > I'll send the export later tonight if no objections.
 > >
 > 
 > Would there be any objections if I commit the patch below so input
 > could be built as a module? 

Under what circumstances is it desirable to allow INPUT=m ?
I'm having a hard time thinking of a usage scenario where it makes sense.

	Dave
-
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/