From owner-freebsd-questions@FreeBSD.ORG Wed Jun 4 22:50:44 2014 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 ESMTPS id 1465FEEE for ; Wed, 4 Jun 2014 22:50:44 +0000 (UTC) Received: from www81.your-server.de (www81.your-server.de [213.133.104.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C6E3F2D3B for ; Wed, 4 Jun 2014 22:50:42 +0000 (UTC) Received: from [92.76.90.49] (helo=michael-think) by www81.your-server.de with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80.1) (envelope-from ) id 1WsK0v-0006qG-U2; Thu, 05 Jun 2014 00:50:34 +0200 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-questions@freebsd.org, "Will Parsons" , gyliamos@gmail.com Subject: Re: ssh + su problem References: <20140601231728.9decb4f8b733c26bf040f963@yahoo.es> <20140604061922.GA2130@La-Habana> Date: Thu, 05 Jun 2014 00:50:26 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Michael Ross" Message-ID: In-Reply-To: User-Agent: Opera Mail/1.0 (Win32) X-Authenticated-Sender: gmx@ross.cx X-Virus-Scanned: Clear (ClamAV 0.98.1/19058/Wed Jun 4 19:31:08 2014) 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: Wed, 04 Jun 2014 22:50:44 -0000 On Wed, 04 Jun 2014 21:30:09 +0200, Will Parsons = wrote: > Matthias Apitz wrote: >> El d?a Tuesday, June 03, 2014 a las 09:48:01PM +0000, Will Parsons = >> escribi?: >> >>> >> % su >>> >> Password: >>> >> su: Sorry >>> >> % >>> >> >>> >>> No - doesn't help. (Again, note that there's no problem su-ing >>> locally, only after loggin in remotely with ssh.) >> >> Try: >> - become root in anther vt-session locally, >> - issue the 'su' command, still without providing a password >> - look as root for the PID of the 'su' and attach something like >> # truss -o /tmp/su.tr -f -p PID >> - provide the password to the 'su' >> - check the file /tmp/su.tr what the 'su' complains about > > Thanks. Although I haven't solved the problem yet, I now know from > the truss output that the immediate cause is that my root password > contains the sequence "'A", and this was getting translated to > meta-A. (It would have course been obvious if the password echo were > not being surpressed.) > > Curiously enough, although translation happens both for Cygwin ssh and= > PuTTY, they do different things. > > On cygwin ssh, if type 'A on the command line, I see: > > \303\201 That's unicode for =C1 ( A with acute ), not 'A ( single-quote + A ), is= n't = it? > > Using PuTTY: > > \301 And that would be ISO-8859-1 for A with acute. > > (which I guess is meta-A) > > I'm not sure where this is coming from, but if all else fails, I think= > I should be able to get around it by changing my root password.