Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 01 Jun 2014 06:28:05 +0100
From:      Dave <davemorgan353@btinternet.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: ssh + su problem
Message-ID:  <ebf33350-4c49-4836-8358-7336942fb497@email.android.com>
In-Reply-To: <op.xgqvd7cvg7njmm@michael-think>
References:  <slrnlokc4u.2it.varro@anukis.local> <op.xgqvd7cvg7njmm@michael-think>

next in thread | previous in thread | raw e-mail | index | archive | help
On 31 May 2014 22:59:57 BST, Michael Ross <gmx@ross.cx> wrote:
>On Sat, 31 May 2014 21:42:23 +0200, Will Parsons
><varro@nodomain.invalid>  
>wrote:
>
>> 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?
>>
>
>Maybe a character encoding issue, any "special" characters in your root
> 
>password?
>
>
>Michael
>_______________________________________________
>freebsd-questions@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to
>"freebsd-questions-unsubscribe@freebsd.org"

There's no need to allow root login.  You can revert that to "no".
--
Dave

GPG/PGP ID: CDB94DA1
From owner-freebsd-questions@FreeBSD.ORG  Sun Jun  1 08:38:07 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 ESMTPS id 88EFF260
 for <freebsd-questions@freebsd.org>; Sun,  1 Jun 2014 08:38:07 +0000 (UTC)
Received: from the-host.seacom.mu (ge-0.ln-01-jnb.za.seacomnet.com
 [41.87.104.245])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B46D4254D
 for <freebsd-questions@freebsd.org>; Sun,  1 Jun 2014 08:38:05 +0000 (UTC)
Received: from localhost ([127.0.0.1] helo=the-host.localnet)
 by the-host.seacom.mu with esmtp (Exim 4.80.1)
 (envelope-from <mark.tinka@seacom.mu>)
 id 1WqyeI-00087N-7t; Sun, 01 Jun 2014 07:49:38 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Reply-To: mark.tinka@seacom.mu
Organization: SEACOM
To: freebsd-questions@freebsd.org,
 tyler@tysdomain.com
Subject: Re: ssh + su problem
Date: Sun, 1 Jun 2014 07:49:34 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <slrnlokc4u.2it.varro@anukis.local>
 <538A3B95.9010605@tysdomain.com>
In-Reply-To: <538A3B95.9010605@tysdomain.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1554328.yaP6cGkxka";
 protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201406010749.37505.mark.tinka@seacom.mu>
Cc: gyliamos@gmail.com
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jun 2014 08:38:07 -0000

--nextPart1554328.yaP6cGkxka
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Saturday, May 31, 2014 10:29:09 PM Littlefield, Tyler=20
wrote:

>   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.

I get this all the time regardless of whether the client is=20
on Windows or UNIX/Linux. I've never had the time to look=20
into it, perhaps I should, some day.

My solution - sudo.=20

"sudo su" will allow you to login as root remotely.

Mark.

--nextPart1554328.yaP6cGkxka
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iQIcBAABAgAGBQJTir7xAAoJEGcZuYTeKm+GukEQAJaChsq/E7sPWAMydmq1Rjou
F3//ZPyzBEI+ayEpddk+EbR08YTXiktTkTImjjEjR9geE5SVv7v9lTCwhKGDgezE
1OWlShbSXqmavviXN/lMTkGVXTdWjjWSNpRaFZP9QTwreth9E+Juj3rVuZ7mZQHR
GJojeysyXm98TDc7pL1JZ+9u2PUY4G/RcwLg4JhUPUTqYk1Of1bjeW3lzgcRrRtv
I/kgc2FNybFu2/UtCFE04YbcPFm29AjDT/WEb9hdjyZ6QHtbWYJrCU6JgRafq5X9
6Q6pjTc8qkY5NnbYgbqvLeBBQuAfaYJNaAQkCZo2OEkAmYKsqk+rYnd/0sg+iR1I
WGHNxpPhBvobt5mQ7sF5ex7RQCNLOynLlxwvg38lcTvImU0H0B8Wx3j4GphKYo2T
6NWiic/ByuTT3s1d8cwcQJ7di8INJXbn5gC5VAunS7Nl01RaCgScAodCU+G2Lrwr
l+swefJFeacpcpKsGXVsEoKLNUuzpU5OZ842ZQGP3cHKhYtJ1GR4zebkesSz0PbJ
JvBgpFbe0OVxuzqeFPOli3uaPscmwP52qmSTZtY19nW2fZ3r6cZraswn4kXyXct1
+SxxtCcO7CCy5FzlbvxhaQabesMeNDre+JOJfyAe3u/S7P0E227UZBpEEIWS7ls+
JDxDXdeTqpjCtQHNER0U
=xpAT
-----END PGP SIGNATURE-----

--nextPart1554328.yaP6cGkxka--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ebf33350-4c49-4836-8358-7336942fb497>