From owner-freebsd-current Sun Sep 17 19: 4:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 22AD437B424 for ; Sun, 17 Sep 2000 19:04:37 -0700 (PDT) Received: (qmail 51200 invoked by uid 1142); 18 Sep 2000 02:04:32 -0000 Date: 17 Sep 2000 19:04:32 -0700 Date: Sun, 17 Sep 2000 19:04:23 -0700 From: Jason Evans To: Konstantin Chuguev Cc: Udo Schweigert , freebsd-current@FreeBSD.ORG Subject: Re: ssh and scp fail connecting to a root account Message-ID: <20000917190423.A28269@canonware.com> References: <20000915163344.A79462@alaska.cert.siemens.de> <39C234CC.668195B@dante.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39C234CC.668195B@dante.org.uk>; from Konstantin.Chuguev@dante.org.uk on Fri, Sep 15, 2000 at 03:40:12PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 15, 2000 at 03:40:12PM +0100, Konstantin Chuguev wrote: > Udo Schweigert wrote: > > > after a fresh build of -current openssh does not work if connecting to the > > root-user. For example (tested from a -stable machine, but the same from > > 4.1-RELEASE): > > Yes, I've been seeing the same thing since the checkout of the SMPng stuff... > No idea why it's happening. I've seen similar things intermittently over the past 10 days, and specifically the same problem for the past three days or so. I'm pretty sure that the problems have been associated with the random device rather than the SMP work specifically. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message