From owner-freebsd-questions@FreeBSD.ORG Mon Oct 14 05:37:50 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D63C937D for ; Mon, 14 Oct 2013 05:37:50 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B8E412B54 for ; Mon, 14 Oct 2013 05:37:50 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VVaqi-0000yJ-EY for freebsd-questions@freebsd.org; Sun, 13 Oct 2013 22:37:48 -0700 Date: Sun, 13 Oct 2013 22:37:48 -0700 (PDT) From: Beeblebrox To: freebsd-questions@freebsd.org Message-ID: <1381729068425-5851636.post@n5.nabble.com> In-Reply-To: <525AF4F5.2080209@fjl.co.uk> References: <1381684110517-5851543.post@n5.nabble.com> <525AF4F5.2080209@fjl.co.uk> Subject: Authorisation Errors on 9.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Oct 2013 05:37:50 -0000 Hi, I Inadvertently posted the gnome-keyring bit. That's almost standard error message on FreeBSD-Gnome. The relevant bit for the error is in fact: slim: gkr-pam: no password is available for user However, the user cannot login on a tty without providing a password. For ssh, the same error and dropped connection occurs for all users. sshd was modified to allow root login. All users have valid home directories defined. From /etc/passwd; I wonder if this has anything to do with it? sshd:*:22:22:Secure Shell Daemon:/var/empty:/usr/sbin/*nologin* >> Could it be a dud /root/.tcshrc? Or /etc/login.conf? The accounts which try to ssh login also login on host proper and do not have any login issues when logging-in directly on host - so I think we can eliminate these problems. Thanks and Regards ----- FreeBSD-9.2-stable_amd64_root-on-zfs_clang-only-world -- View this message in context: http://freebsd.1045724.n5.nabble.com/Authorisation-Errors-on-9-2-tp5851543p5851636.html Sent from the freebsd-questions mailing list archive at Nabble.com.