From owner-freebsd-questions@FreeBSD.ORG Wed Jun 4 19:30:27 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 991E473C for ; Wed, 4 Jun 2014 19:30:27 +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 507722735 for ; Wed, 4 Jun 2014 19:30:27 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WsGtB-0006Pw-9P for freebsd-questions@freebsd.org; Wed, 04 Jun 2014 21:30:21 +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 ; Wed, 04 Jun 2014 21:30:21 +0200 Received: from gyliamos by 65.75.36.70 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Jun 2014 21:30:21 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Will Parsons Subject: Re: ssh + su problem Date: Wed, 4 Jun 2014 19:30:09 +0000 (UTC) Lines: 44 Message-ID: References: <20140601231728.9decb4f8b733c26bf040f963@yahoo.es> <20140604061922.GA2130@La-Habana> 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: Wed, 04 Jun 2014 20:47:37 +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: Wed, 04 Jun 2014 19:30:27 -0000 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 Using PuTTY: \301 (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. -- Will