From owner-freebsd-hackers Fri Sep 13 13:51:49 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99E0137B400; Fri, 13 Sep 2002 13:51:45 -0700 (PDT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35B1D43E6A; Fri, 13 Sep 2002 13:51:45 -0700 (PDT) (envelope-from sam@errno.com) Received: from melange (melange.errno.com [66.127.85.82]) (authenticated bits=0) by ebb.errno.com (8.12.5/8.12.1) with ESMTP id g8DKpi1H026641 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 13 Sep 2002 13:51:44 -0700 (PDT)?g (envelope-from sam@errno.com)œ X-Authentication-Warning: ebb.errno.com: Host melange.errno.com [66.127.85.82] claimed to be melange Message-ID: <305701c25b67$5ebc19e0$52557f42@errno.com> From: "Sam Leffler" To: "Stacy Millions" , Cc: References: <3D822EB8.4010201@millions.ca> Subject: Re: kern_random interface Date: Fri, 13 Sep 2002 13:51:44 -0700 Organization: Errno Consulting MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Am I on the right track here? I have looked at the Hardware Crypto > Support stuff and I don't think anything I'm doing or purposing > conflicts with it. > If you looked at my stuff then you hopefully saw that I added: void add_true_randomness(int val) { add_entropy_word(&random_state, val); random_state.entropy_count += 8*sizeof (val); if (random_state.entropy_count > POOLBITS) random_state.entropy_count = POOLBITS; selwakeup(&random_state.rsel); } to kern/kern_random.c and used it to feed data from h/w RNG's that appear on various crypto parts. I'm working on getting this stuff into -current right now and will eventually MFC the h/w crypto support to -stable after the 4.7 release. So it would be good to use the same interface, right? Feel free to correspond directly; I'm not sure everyone wants to hear these details. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message