From owner-freebsd-hackers Mon Nov 23 14:33:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26583 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 14:33:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (48-sweet.camalott.com [208.239.153.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26571 for ; Mon, 23 Nov 1998 14:33:26 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id QAA63181; Mon, 23 Nov 1998 16:33:12 -0600 (CST) (envelope-from joelh) To: Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: /dev/random usage References: <98Nov24.080435est.40327@border.alcanet.com.au> From: Joel Ray Holveck Date: 23 Nov 1998 16:33:10 -0600 In-Reply-To: Peter Jeremy's message of "Tue, 24 Nov 1998 08:05:01 +1100" Message-ID: <86emqum449.fsf@detlev.UUCP> Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Speaking of such things, what are some apps that use /dev/random, or >> at least have hooks to use a random device? > Going thru the 3.0-RELEASE source tree, the following programs all use > srandomdev(3) - which gives you a pseudo-random sequence starting from [snip] > Also arc4random(3) uses /dev/urandom for seeding it - and arc4random(3) > is used by mktemp(3). That's interesting. What about apps not in our tree? Mostly, I'm wondering what apps need large quantities of completely random numbers, and use our hooks to get it. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message