From owner-freebsd-security@FreeBSD.ORG Fri Sep 19 12:50:39 2003 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76A5516A4BF for ; Fri, 19 Sep 2003 12:50:39 -0700 (PDT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9742543FBF for ; Fri, 19 Sep 2003 12:50:37 -0700 (PDT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 4E3F5653D8; Fri, 19 Sep 2003 20:50:36 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 38654-03; Fri, 19 Sep 2003 20:50:35 +0100 (BST) Received: from saboteur.dek.spc.org (lardystuffer.demon.co.uk [212.228.40.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 517C6653C6; Fri, 19 Sep 2003 20:50:34 +0100 (BST) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 49C6B1D; Fri, 19 Sep 2003 20:50:25 +0100 (BST) Date: Fri, 19 Sep 2003 20:50:25 +0100 From: Bruce M Simpson To: Michael Sierchio Message-ID: <20030919195025.GB3815@saboteur.dek.spc.org> Mail-Followup-To: Michael Sierchio , freebsd-security@freebsd.org References: <200309190802.h8J82bfq006549@grimreaper.grondar.org> <3F6B1950.8090304@tenebras.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F6B1950.8090304@tenebras.com> Organization: SPC cc: freebsd-security@freebsd.org Subject: Re: [Fwd: Re: FreeBSD Security Advisory FreeBSD-SA-03:12.openssh] X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2003 19:50:39 -0000 On Fri, Sep 19, 2003 at 07:57:20AM -0700, Michael Sierchio wrote: > Question, since I haven't looked at the code -- does it honor the > /dev/crypto interface? Since, if a HW RBG is included in a crypto > device, it should be used to help stir the pot. Stacy Millions had a driver in the works to support the Intel i8xx FWH HW RNG. As far as I know it hasn't been committed, I'd certainly like to see this code updated. BMS