From owner-freebsd-current Mon Sep 18 6:58:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id DF6F837B424; Mon, 18 Sep 2000 06:58:08 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.0/8.9.3) id e8IDvf206856; Mon, 18 Sep 2000 15:57:41 +0200 (CEST) (envelope-from asmodai) Date: Mon, 18 Sep 2000 15:57:41 +0200 From: Jeroen Ruigrok van der Werven To: Alexander Leidinger Cc: current@FreeBSD.ORG, kris@FreeBSD.ORG Subject: Re: updated OpenSSH & pam_ssh, the old bug is back Message-ID: <20000918155741.K4858@lucifer.bart.nl> References: <200009161449.e8GEnCn01662@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009161449.e8GEnCn01662@Magelan.Leidinger.net>; from Alexander@Leidinger.net on Sat, Sep 16, 2000 at 04:49:10PM +0200 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000916 17:10], Alexander Leidinger (Alexander@Leidinger.net) wrote: >after the update of OpenSSH xdm crashes if I enable pam_ssh in pam.conf. >I fixed this in the old version, but it seems the bug is back. > >I have a look at it and try to produce a patch again. You mean that bug which you reported and produced a patch and which I subsequently committed? The malloc.conf -> AJ resulted coredump one? -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Grant me the serenity to accept the things I cannot change, courage to change the things I can, and wisdom to know the difference... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message