From owner-freebsd-arch@FreeBSD.ORG Wed Aug 7 19:27:42 2013 Return-Path: Delivered-To: freebsd-arch@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 C7B34A17; Wed, 7 Aug 2013 19:27:42 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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 A797C2319; Wed, 7 Aug 2013 19:27:42 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r77JRabm007148; Wed, 7 Aug 2013 12:27:36 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r77JRaoc007147; Wed, 7 Aug 2013 12:27:36 -0700 (PDT) (envelope-from sgk) Date: Wed, 7 Aug 2013 12:27:36 -0700 From: Steve Kargl To: obrien@freebsd.org, secteam@freebsd.org, freebsd-arch@freebsd.org, Arthur Mesh Subject: Re: random(4) plugin infrastructure for mulitple RNG in a modular fashion Message-ID: <20130807192736.GA7099@troutmask.apl.washington.edu> References: <20130807182858.GA79286@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130807182858.GA79286@dragon.NUXI.org> User-Agent: Mutt/1.5.21 (2010-09-15) 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: Wed, 07 Aug 2013 19:27:42 -0000 On Wed, Aug 07, 2013 at 11:28:58AM -0700, David O'Brien wrote: > > * Make Yarrow an optional kernel component -- enabled by "YARROW_RNG" > option. The files sha2.c, hash.c, randomdev_soft.c and yarrow.c > comprise yarrow. random(4) device doesn't really depend on > rijndael-*. Yarrow, however, does. > > * If the kernel doesn't have any random_adaptor adapters present then > the creation of /dev/random is postponed until next random_adaptor > is kldload'ed. My kernel config files have included the following 2 lines for ages: makeoptions NO_MODULES device random If I try to build a new kernel under your scheme, will the build die with an error about a missing option? If the answer is 'no', then the yarrow adaptor should be opt-out. -- steve