From owner-freebsd-security Thu Jun 27 6:37:25 2002 Delivered-To: freebsd-security@freebsd.org Received: from a2.scoop.co.nz (aurora.scoop.co.nz [203.96.152.68]) by hub.freebsd.org (Postfix) with ESMTP id F06BD37B400 for ; Thu, 27 Jun 2002 06:37:18 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by a2.scoop.co.nz (8.12.2/8.12.2) with ESMTP id g5RDbBMx084490; Fri, 28 Jun 2002 01:37:11 +1200 (NZST) (envelope-from andrew@scoop.co.nz) Date: Fri, 28 Jun 2002 01:37:11 +1200 (NZST) From: Andrew McNaughton X-X-Sender: andrew@a2 To: Maxim Kozin Cc: security@FreeBSD.ORG Subject: Re: openssh-portable and s/key passwords In-Reply-To: Message-ID: <20020628013529.I83962-100000@a2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 26 Jun 2002, Maxim Kozin wrote: > Problem: setup openssh + pam(some self-write module) > When I don't create full chroot enviromnet in /usr/local/empty, Have you changed this to use /usr/local/empty? It wanted me to set this up as /var/empty. > sshd -d -d -d fail in start_pam. > All symbol in my_pam.so must be resolved on privsep step, because > copy in chroot all need libs,/etc/pam.conf and /etc/passwd > Now I can see, that pam started, make succefuly auth. > BUt session disconected with diagnostic: > debug3: monitor_read: checking request 24 > debug3: mm_send_keystate: Finished sending state > monitor_read: unsupported request: 24 > debug1: Calling cleanup 0x806d98c(0x0) > > "Request type 24" is some about tty/pty ? Andrew McNaughton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message