From owner-freebsd-arch@FreeBSD.ORG Fri Aug 9 06:41:23 2013 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0A8C9F6A; Fri, 9 Aug 2013 06:41:23 +0000 (UTC) (envelope-from sjg@juniper.net) Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe001.messaging.microsoft.com [216.32.181.181]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A9B5D2161; Fri, 9 Aug 2013 06:41:22 +0000 (UTC) Received: from mail11-ch1-R.bigfish.com (10.43.68.236) by CH1EHSOBE009.bigfish.com (10.43.70.59) with Microsoft SMTP Server id 14.1.225.22; Fri, 9 Aug 2013 06:26:06 +0000 Received: from mail11-ch1 (localhost [127.0.0.1]) by mail11-ch1-R.bigfish.com (Postfix) with ESMTP id 89281340271; Fri, 9 Aug 2013 06:26:06 +0000 (UTC) X-Forefront-Antispam-Report: CIP:66.129.224.51; KIP:(null); UIP:(null); IPV:NLI; H:P-EMF01-SAC.jnpr.net; RD:none; EFVD:NLI X-SpamScore: 3 X-BigFish: VPS3(zzzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6h1082kzzz2fh2a8h668h839hd25hf0ah1288h12a5h12a9h12bdh12e5h137ah139eh13b6h1441h14ddh1504h1537h162dh1631h1758h1898h18e1h1946h19b5h1ad9h1b0ah1b2fh1b88h1fb3h1d0ch1d2eh1d3fh1de2h1dfeh1dffh1e23h1fe8h1155h) Received-SPF: pass (mail11-ch1: domain of juniper.net designates 66.129.224.51 as permitted sender) client-ip=66.129.224.51; envelope-from=sjg@juniper.net; helo=P-EMF01-SAC.jnpr.net ; SAC.jnpr.net ; Received: from mail11-ch1 (localhost.localdomain [127.0.0.1]) by mail11-ch1 (MessageSwitch) id 1376029565139452_11367; Fri, 9 Aug 2013 06:26:05 +0000 (UTC) Received: from CH1EHSMHS035.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.234]) by mail11-ch1.bigfish.com (Postfix) with ESMTP id 1C41A1C0047; Fri, 9 Aug 2013 06:26:05 +0000 (UTC) Received: from P-EMF01-SAC.jnpr.net (66.129.224.51) by CH1EHSMHS035.bigfish.com (10.43.70.35) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 9 Aug 2013 06:26:05 +0000 Received: from magenta.juniper.net (172.17.27.123) by P-EMF01-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 8 Aug 2013 23:26:03 -0700 Received: from chaos.jnpr.net (chaos.jnpr.net [172.24.29.229]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id r796Q3L22631; Thu, 8 Aug 2013 23:26:03 -0700 (PDT) (envelope-from sjg@juniper.net) Received: from chaos.jnpr.net (localhost [127.0.0.1]) by chaos.jnpr.net (Postfix) with ESMTP id 2053E58097; Thu, 8 Aug 2013 23:26:03 -0700 (PDT) To: , Mark R V Murray , Arthur Mesh , Steve Kargl , , Subject: Re: random(4) plugin infrastructure for mulitple RNG in a modular fashion In-Reply-To: <20130809013346.GG95000@dragon.NUXI.org> References: <20130807182858.GA79286@dragon.NUXI.org> <20130807192736.GA7099@troutmask.apl.washington.edu> <5203968D.7060508@freebsd.org> <7018AAA9-0A88-430F-96B7-867E5F529B36@bsdimp.com> <50BE6942-CC39-413C-8E14-C6B93440901B@grondar.org> <20130808211657.GC95000@dragon.NUXI.org> <94E41175-EF09-47D1-9661-9AF04E8FA9A0@grondar.org> <20130808215853.2288458097@chaos.jnpr.net> <20130809013346.GG95000@dragon.NUXI.org> Comments: In-reply-to: "David O'Brien" message dated "Thu, 08 Aug 2013 18:33:46 -0700." From: "Simon J. Gerraty" X-Mailer: MH-E 7.82+cvs; nmh 1.3; GNU Emacs 22.3.1 Date: Thu, 8 Aug 2013 23:26:03 -0700 Message-ID: <20130809062603.2053E58097@chaos.jnpr.net> MIME-Version: 1.0 Content-Type: text/plain X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 06:41:23 -0000 On Thu, 8 Aug 2013 18:33:46 -0700, "David O'Brien" writes: >I may have misunderstood what you're saying. But if not, you're >not allowing for one using .ko's to have this functionality. I'm simply saying that if you can arrange for a build failure instead of producing a toxic system, it becomes much simpler to assure folk that you cannot do them harm with these changes. If you can't then it might be wise to leave a default like yarrow in place, that can be used as a fallback if no (or until) suitable .ko's are loaded? >'sysctl kern.random.adaptors' showing an empty list does provide >a bread crumb. /etc/rc.d/initrandom could certainly check this >value and complain loudly. That's probably a bit too late though isn't it.