From owner-freebsd-security Mon Jul 16 16:31:47 2001 Delivered-To: freebsd-security@freebsd.org Received: from scooby.netsville.com (scooby.netsville.com [206.27.96.131]) by hub.freebsd.org (Postfix) with ESMTP id AA9DF37B405 for ; Mon, 16 Jul 2001 16:31:43 -0700 (PDT) (envelope-from brandon@vv.com) Received: from brandon by scooby.netsville.com with local (Exim 3.22 #1 (Debian)) id 15MHq1-0002kq-00; Mon, 16 Jul 2001 19:31:41 -0400 Date: Mon, 16 Jul 2001 19:31:40 -0400 From: Micah Brandon To: alexus Cc: freebsd-security@freebsd.org Subject: Re: out of entropy Message-ID: <20010716193140.Q6318@vv.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01c601c10e4b$e20d19d0$0d00a8c0@alexus> User-Agent: Mutt/1.3.18i Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Here is a work-around I've used in the past. Create a "random" file from the output of various commands like this: $ dd if=/dev/urandom of=my_random_file count=1024 $ date >>my_random_file $ netstat -a >>my_random_file $ df -k >>my_random_file Then, feed the file to dnssec-keygen with the "-r " option. Obviously, this is not the best "randomness", but it will create a key for you. Just keep secret what output you use in your random file :) * alexus (ml@db.nexgen.com) [010716 19:08]: > i've tryed that... > > su-2.05# rndcontrol > rndcontrol: interrupts in use: 10 15 > su-2.05# > > still same thing > -- Micah Brandon brandon@vv.com Netsville, Inc. http://www.netsville.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message