From owner-freebsd-current@FreeBSD.ORG Sat Sep 7 21:45:15 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E5B7099C; Sat, 7 Sep 2013 21:45:15 +0000 (UTC) (envelope-from mark@grondar.org) Received: from gromit.grondar.org (grandfather.grondar.org [IPv6:2a01:348:0:15:5d59:5c20:0:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A61C126F5; Sat, 7 Sep 2013 21:45:15 +0000 (UTC) Received: from graveyard.grondar.org ([88.96.155.33] helo=gronkulator.grondar.org) by gromit.grondar.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1VIQJc-000Dte-CI; Sat, 07 Sep 2013 22:45:13 +0100 Subject: Re: random(4) update causes mips compile fail | mips boot fail Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Content-Type: multipart/signed; boundary="Apple-Mail=_0DF2CB3D-CBBE-440F-99BD-85C8FD521DE8"; protocol="application/pgp-signature"; micalg=pgp-sha512 From: Mark R V Murray In-Reply-To: <1378589511.1111.529.camel@revolution.hippie.lan> Date: Sat, 7 Sep 2013 22:45:11 +0100 Message-Id: References: <1378572186.1588.5.camel@localhost> <24DB010A-F374-491B-9203-FDDD7EA14A51@grondar.org> <1378579011.1588.16.camel@localhost> <9240BEF1-2791-4D58-A422-08AEF1CD306C@grondar.org> <1378586316.1111.524.camel@revolution.hippie.lan> <618CA386-7444-4631-A69B-7FD2F22C91E6@grondar.org> <1378589511.1111.529.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1508) X-SA-Score: -2.2 X-Mailman-Approved-At: Sun, 08 Sep 2013 00:18:23 +0000 Cc: Adrian Chadd , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 07 Sep 2013 21:45:16 -0000 --Apple-Mail=_0DF2CB3D-CBBE-440F-99BD-85C8FD521DE8 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 7 Sep 2013, at 22:31, Ian Lepore wrote: > Those of us who have to cope with limited systems will fix our config > for those systems; that part of it shouldn't be your problem beyond > providing us with a knob. If there is NO random number generator, then /dev/random blocks. Period. If you don't want to block, don't read /dev/random. If you have an RNG loaded (like Yarrow), the intent is that it will block-until-secure, but you can insta-unblock it by writing to it. The intent is that early in the boot, while running all the /etc/rc.d/* stuff, you write anything you like (hopefully random crud) to the device and it seeds itself with what it gets. At file close after the write, it unblocks. So at the minimum, you can unblock Yarrow by doing $ echo '' > /dev/random ... as soon as the device is active. There is your knob. M -- Mark R V Murray --Apple-Mail=_0DF2CB3D-CBBE-440F-99BD-85C8FD521DE8 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) Comment: GPGTools - http://gpgtools.org iQCVAwUBUiueZ958vKOKE6LNAQpweAP/UGQnbVOT0Qh+4nrldKvK9dzsdbj0AAZm wuBuITlTrrgioHWxrXlOAsp80Xa7CaOvTGLhNoVIP7qfW74klWTGJ7Jpej8aeVtC fsOZq7D43bDqremOV4HSTu11oovhwtJx4QsD6s59nUiU0SoDgo30B+xYYFqRnRSz pwVQJ7pHqfU= =VHNS -----END PGP SIGNATURE----- --Apple-Mail=_0DF2CB3D-CBBE-440F-99BD-85C8FD521DE8--