Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by krbdev.mit.edu (8.9.3) with ESMTP id UAA06481; Tue, 29 Oct 2002 20:17:15 -0500 (EST) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id UAA12847 for ; Tue, 29 Oct 2002 20:17:15 -0500 (EST) Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.7.71]) by central-city-carrier-station.mit.edu (8.9.2/8.9.2) with ESMTP id UAA28785; Tue, 29 Oct 2002 20:17:14 -0500 (EST) Received: from all-in-one.mit.edu (ALL-IN-ONE.MIT.EDU [18.18.1.71]) by manawatu-mail-centre.mit.edu (8.9.2/8.9.2) with ESMTP id UAA18594; Tue, 29 Oct 2002 20:17:14 -0500 (EST) Received: (from raeburn@localhost) by all-in-one.mit.edu (8.9.3) id UAA22190; Tue, 29 Oct 2002 20:17:14 -0500 To: krb5-bugs@MIT.EDU Subject: need to disable /dev/random use for testing From: Ken Raeburn Date: Tue, 29 Oct 2002 20:17:14 -0500 Message-Id: Lines: 11 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-RT-Original-Encoding: us-ascii Content-Length: 609 On relatively idle machines, nightly tests run via cron are failing because kadmin takes too long to initialize at startup, because it blocks reading from /dev/random. For testing purposes, we don't care how good the random numbers are, as long as they're at least "sort of" good; using /dev/urandom is more than adequate. A new config file (krb5.conf probably) option to explicitly turn off the use of /dev/random should be created. Probably using "insecure" and "entropy" in the name, something like that. Whether the application-level code or the crypto library code should act on it is to be decided.