From owner-cvs-all Mon Jun 26 17:35:19 2000 Delivered-To: cvs-all@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 603B037BD89; Mon, 26 Jun 2000 17:35:14 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 298184C; Mon, 26 Jun 2000 20:35:12 -0400 (AST) Message-ID: <3957F6C0.B8D8E006@vangelderen.org> Date: Mon, 26 Jun 2000 20:35:12 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Peter Wemm , Mark Murray , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/usr.sbin Makefile src/usr.sbin/rndcontrol Makefile random.4 rndcontrol.8 rndcontrol.c References: <20000626210416.324691CD7@overcee.netplex.com.au> <200006262227.QAA28257@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <20000626210416.324691CD7@overcee.netplex.com.au> Peter Wemm writes: > : Err.. why? We now have a generic place to hook into at the nexus if the > : driver approves. For shared irqs, we can check that all handlers are OK > : with it. We have flags available.. > > Even without flags, we can make a simple kobj_true() and > kobj_false(). The genertic nexus thing could then ask the drivers > "Can I use your IRQ for entropty?" with some method > (device_irq_random, say) and the driver would default to > using the kobj_true method (return 1;) for this, but those drivers > that don't think their interrupts will be random enough, can > implemetne device_irq_random as kobj_false. Urm, we're talking security here. The default should be false unless the driver knows it's IRQ makes for a reasonable entropy source. For shared IRQs you would need to "AND" all the return values together. Eventually it may be better to have the device export an entropy pseudo-device itself. We would need those for pure entropy gathering devices anyway but even in the case of a network driver it can be useful: the driver has access to it's IRQ timings as well as network statistics from which entropy can be distilled. The network driver could even disable it's entropy device interface unless the link is actually up and data is arriving. My EC$ 0.02, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message