From owner-freebsd-questions@FreeBSD.ORG Sat May 31 19:42:44 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 484336F1 for ; Sat, 31 May 2014 19:42:44 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0796F26EB for ; Sat, 31 May 2014 19:42:43 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WqpAt-0000sM-8X for freebsd-questions@freebsd.org; Sat, 31 May 2014 21:42:39 +0200 Received: from 65.75.36.70 ([65.75.36.70]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 31 May 2014 21:42:39 +0200 Received: from gyliamos by 65.75.36.70 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 31 May 2014 21:42:39 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Will Parsons Subject: ssh + su problem Date: Sat, 31 May 2014 19:42:23 +0000 (UTC) Lines: 22 Message-ID: Reply-To: gyliamos@gmail.com X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 65.75.36.70 User-Agent: slrn/1.0.1 (FreeBSD) X-Mailman-Approved-At: Sat, 31 May 2014 20:16:41 +0000 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 May 2014 19:42:44 -0000 I have a problem in that I cannot su to root on a FreeBSD machine remotely from a Windows machine. Note that the user I'm logging in as *is* a member of the wheel group (and I can su locally just fine). Symptoms are: % su Password: su: Sorry % Although I *think* the purpose of the sshd option "PermitRootLogin" is to (dis)allow *direct* root ssh logins, I changed it to "yes" anyway in sshd_config, but that doesn't seem to be the problem. I'm inclined to think this a server-side configuration issue, since I get the same result whether I use Cygwin ssh or PuTTY to log in remotely to the FreeBSD machine. Any ideas of what might be wrong? -- Will