From owner-freebsd-current@FreeBSD.ORG Thu May 17 20:38:29 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 860951065800; Thu, 17 May 2012 20:38:29 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9D4B68FC20; Thu, 17 May 2012 20:38:28 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA14319; Thu, 17 May 2012 23:38:24 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1SV7Sq-0002sc-LM; Thu, 17 May 2012 23:38:24 +0300 Message-ID: <4FB561BF.2090404@FreeBSD.org> Date: Thu, 17 May 2012 23:38:23 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120503 Thunderbird/12.0.1 MIME-Version: 1.0 To: Bruce Cran References: <4FB14C48.1030002@cran.org.uk> In-Reply-To: <4FB14C48.1030002@cran.org.uk> X-Enigmail-Version: 1.5pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current Subject: Re: "random device not loaded; using insecure entropy" during boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2012 20:38:29 -0000 on 14/05/2012 21:17 Bruce Cran said the following: > While booting -current I noticed a new warning introduced in r230230** > (though it's not > in 'dmesg' once booted): > > FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 4 > cpu3 (AP): APIC ID: 5 > random device not loaded; using insecure entropy > > I guess something's wanting random data before its been initialized? Once > booted kern.random shows that it is loaded and working. It seems that the message is triggered by __stack_chk_init. I am not sure if we really need a "secure" random value there. -- Andriy Gapon