From owner-freebsd-current Sun Jul 30 18:48:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 111CE37B954 for ; Sun, 30 Jul 2000 18:48:07 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p26-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.155]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id KAA22000; Mon, 31 Jul 2000 10:47:36 +0900 (JST) Message-ID: <3984DAC1.4ACBF964@newsguy.com> Date: Mon, 31 Jul 2000 10:47:45 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: phkmalloc & pam_ssh & xdm References: <200007301231.OAA54019@Magelan.Leidinger.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Leidinger wrote: > > Hi, > > pam_ssh isn't able to start ssh-agent if you use > ---snip--- > xdm session sufficient pam_ssh.so > ---snip--- > in /etc/pam.conf. With "malloc.conf -> aj" it seems to work. > > grep pam /var/log/messages: > ---snip--- > Jul 30 00:54:04 Magelan -:0: unable to resolve symbol: pam_sm_chauthtok > Jul 30 00:54:05 Magelan -:0: pam_ssh: could not connect to agent > ---snip--- > > Is someone else able to reproduce this? If that's the case, you have a bug. Not one easy to trace, though... :-( -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@white.bunnies.bsdconspiracy.net Satan was once an angel, Gates started by writing a BASIC interpreter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message