Date: Fri, 13 Jul 2018 17:11:51 +0200 From: Dirk-Willem van Gulik <dirkx@webweaving.org> To: Ian Lepore <ian@freebsd.org> Cc: cem@freebsd.org, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Limits to seeding /dev/random | random(4) Message-ID: <84E1C233-5855-43DC-BC58-CAFFA216D1D7@webweaving.org> In-Reply-To: <1531489904.66719.43.camel@freebsd.org> References: <3A988D26-7B08-4301-8176-B0ED8A559420@webweaving.org> <1531317515.66719.20.camel@freebsd.org> <20180712165751.1e5b8e24@gumby.homeunix.com> <7C42CD28-078F-4AF6-90F2-5E951F8386D5@webweaving.org> <CAG6CVpX1DnB7KDigG=wMPROM6vvdw0LB005u6d3c29Dbp7NhTw@mail.gmail.com> <55685C1F-4711-40C7-8EB4-2930BF8C9884@webweaving.org> <CAG6CVpW=gXK-a7RAmDm=xBb3WP=bK3sLxOTBm3r0Y=ES4KzWPg@mail.gmail.com> <1531489904.66719.43.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 13 Jul 2018, at 15:51, Ian Lepore <ian@freebsd.org> wrote: >=20 > On Thu, 2018-07-12 at 11:40 -0700, Conrad Meyer wrote: >> Identical results are very troubling. Maybe your readonly >> filesystems >> contain a static "entropy" file that is being fed in every boot (with Most certainly not. >> identical contents)? If so, you definitely want to remove that >> during >> image generation. That, in tandem with few other sources of entropy, >> could explain identical results. I suspect this to be the issue. >=20 > I have been reporting for years that certain kinds of embedded systems > lead to zero entropy available at boot, including the fact that the .. > It happens. Embedded systems are a different world, and if entropy is > important, sometimes we have to go out of our way to provide some. In our case it is merely a low end machine - but diskless, read-only and = with hardly any perifials. Dw.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?84E1C233-5855-43DC-BC58-CAFFA216D1D7>