From owner-freebsd-current Sun Sep 17 19: 7: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id CD56E37B422; Sun, 17 Sep 2000 19:06:58 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id TAA24987; Sun, 17 Sep 2000 19:06:58 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 17 Sep 2000 19:06:58 -0700 (PDT) From: Kris Kennaway To: Jason Evans Cc: Konstantin Chuguev , Udo Schweigert , freebsd-current@FreeBSD.ORG Subject: Re: ssh and scp fail connecting to a root account In-Reply-To: <20000917190423.A28269@canonware.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 Sep 2000, Jason Evans wrote: > 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. Well, the crash is apparently due to malloc flags - remove the /etc/malloc.conf link and it may work better. I've only seen this once, and when I tried to run sshd under gdb it went away, and now I can't reproduce it again. :-( Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message