From owner-freebsd-questions@FreeBSD.ORG Fri Aug 11 01:14:30 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B89B16A4DD for ; Fri, 11 Aug 2006 01:14:30 +0000 (UTC) (envelope-from mes5048@verizon.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0AE643D45 for ; Fri, 11 Aug 2006 01:14:29 +0000 (GMT) (envelope-from mes5048@verizon.net) Received: from puma ([71.246.26.221]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0J3T00BWX7FOGY02@vms046.mailsrvcs.net> for freebsd-questions@freebsd.org; Thu, 10 Aug 2006 20:14:13 -0500 (CDT) Date: Thu, 10 Aug 2006 21:22:11 -0400 From: "Matt Schwartz" To: Message-id: <000001c6bce4$92a24030$6400000a@puma> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Mailer: Microsoft Office Outlook 11 Thread-index: Aca85JItHIxoKKU7QRqs73BUw0HiYg== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: pam_krb5 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2006 01:14:30 -0000 Hello list, I seem to be having a problem with pam_krb5.so. It works fine on console logins. However, when I ssh into my freebsd server from another computer, tickets are not issued. I have uncommented the pam_krb5.so entries in the sshd pam file. Otherwise, the sshd pam file has been left stock. I know I have a working kerberos install because kinit, klist, and kdestory all work. What might I have missed? I have left the sshd_config unchanged. Any guidance would be appreciated. I have even added a host principle for the client and still no effect. The strange thing is that there are no errors being thrown to /var/log/messages or /var/log/security. If anyone else has seen this, I would really like some insight. Thanks Matt