On Mon, Jan 4, 2016 at 3:44 PM, Mark Saad wrote:
> All
> At NYC*BUG we are looking into a warning seen on FreeBSD 10-STABLE amd64
> starting at or about r292122 and still up till r292855.
>
> On boot dmesg logs the following warning not seen on 10.2-RELEASE amd64.
>
>
On Tue, Jan 5, 2016 at 8:45 AM, Adam Vande More
wrote:
> On Mon, Jan 4, 2016 at 3:44 PM, Mark Saad wrote:
>
>> All
>> At NYC*BUG we are looking into a warning seen on FreeBSD 10-STABLE amd64
>> starting at or about r292122 and still up till
On 2016-Jan-04 16:44:49 -0500, Mark Saad 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
On Tue, Jan 5, 2016 at 2:00 PM, Peter Jeremy wrote:
> On 2016-Jan-04 16:44:49 -0500, Mark Saad 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
Mark,
> At NYC*BUG we are looking into a warning seen on FreeBSD 10-STABLE amd64
> starting at or about r292122 and still up till r292855.
> random device not loaded; using insecure entropy
I noticed this message a while back and again yesterday on my i386 which
runs no modules, just a custom
All
At NYC*BUG we are looking into a warning seen on FreeBSD 10-STABLE amd64
starting at or about r292122 and still up till r292855.
On boot dmesg logs the following warning not seen on 10.2-RELEASE amd64.
random device not loaded; using insecure entropy
The full dmesg can be seen here