Date: Thu, 8 Aug 2013 14:58:53 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Mark R V Murray <mark@grondar.org> Cc: Arthur Mesh <arthurmesh@gmail.com>, secteam@freebsd.org, Steve Kargl <sgk@troutmask.apl.washington.edu>, freebsd-arch@freebsd.org Subject: Re: random(4) plugin infrastructure for mulitple RNG in a modular fashion Message-ID: <20130808215853.2288458097@chaos.jnpr.net> In-Reply-To: <94E41175-EF09-47D1-9661-9AF04E8FA9A0@grondar.org> References: <20130807182858.GA79286@dragon.NUXI.org> <20130807192736.GA7099@troutmask.apl.washington.edu> <CAGE5yCq%2Bs6kYtVYyxi27RAqPmvpV42nNNykm2%2B2x1EJGCihYXw@mail.gmail.com> <5203968D.7060508@freebsd.org> <7018AAA9-0A88-430F-96B7-867E5F529B36@bsdimp.com> <50BE6942-CC39-413C-8E14-C6B93440901B@grondar.org> <20130808211657.GC95000@dragon.NUXI.org> <94E41175-EF09-47D1-9661-9AF04E8FA9A0@grondar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Our approach is mechanism over policy. That is, give the user the >> choice of if their HW should be used directly or fed into the SW PRNG. > >I don't see a problem with that either, as long as there are no nasty >surprises like the possibility of getting no RNG at all, and not being >in a position to notice. If there are bread crumbs to show whether an RNG is present or not in the output from config, it should be feasible to fail the build which as others have noted would be a "good thing"[TM] vs producing a toxic kernel.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130808215853.2288458097>