Date: Tue, 5 Jan 2016 14:11:21 -0500 From: Mark Saad <nonesuch@longcount.org> To: Peter Jeremy <peter@rulingia.com> Cc: FreeBSD-Stable ML <freebsd-stable@freebsd.org> Subject: Re: dev/random warning on 10-STABLE after r292122 up till r292855 Message-ID: <CAMXt9NbPkn9Vf92-tEvbmJgvtwS0sLmK2RAf6-eUFmOjmxvx_w@mail.gmail.com> In-Reply-To: <20160105190023.GF81231@server.rulingia.com> References: <CAMXt9NYVsryEH7JAY3wt6z67oONf=uvXWTdhUzsUSZbG0nZv3g@mail.gmail.com> <20160105190023.GF81231@server.rulingia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 5, 2016 at 2:00 PM, Peter Jeremy <peter@rulingia.com> wrote: > On 2016-Jan-04 16:44:49 -0500, Mark Saad <nonesuch@longcount.org> wrote: > >On boot dmesg logs the following warning not seen on 10.2-RELEASE amd64. > > > >random device not loaded; using insecure entropy > > When I first noticed this, I investigated and worked out that it's > related to how the random device initialises itself and its data and > entropy sources. In particular, it reflects the state of the random > device at that point in time, not at any later point when random data > is actually requested. > > I agree that the wording of this message could unnecessarily alarm a > sysadmin and think it could be done better. IMHO, this sort of > alamist message should only be output if there is no decent entropy > source available when the random device is unblocked. > > -- > Peter Jeremy > Peter I agree it looks like its not really a big deal; what I cant find is what changed to make this even print out. The commits for this warning are from a long time ago. Off hand they are from 2014 or 2012. There were no changes to sys/dev/random in as much time; so I cant figure out what changed to make this even print out. -- mark saad | nonesuch@longcount.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMXt9NbPkn9Vf92-tEvbmJgvtwS0sLmK2RAf6-eUFmOjmxvx_w>