From owner-freebsd-current Wed Jul 12 9:36:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 18FAE37BF86 for ; Wed, 12 Jul 2000 09:36:18 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 6C48E51; Wed, 12 Jul 2000 12:36:12 -0400 (AST) Message-ID: <396C9E7C.781ABA6@vangelderen.org> Date: Wed, 12 Jul 2000 12:36:12 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Galt Cc: Mark Murray , freebsd-current@FreeBSD.ORG Subject: Re: ssh not working after upgrading OS? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Galt wrote: > On Wed, 12 Jul 2000, Mark Murray wrote: > > > > You are probably using a -CURRENT with a broken randomness > > > device. For more information you can try and search the > > > mailing list archives. > > > > No - he has _no_ randomness device. > > Isn't there an add-on daemon for that, ESD or somesuch? The OpenSSL docs > mention it. Yes and no. That daemon is a 'hack' for systems that lack a randomness device. You don't want to use it when you do have a good /dev/random. FreeBSD has a /dev/random except that it has been broken for a while whilst MarkM brought it up to snuff. The mailing list archives ought to contain all of the details one needs to fix this temporary problem. No need to resort to EGD, just tweak some config. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message