Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 05 Jun 2014 00:50:26 +0200
From:      "Michael Ross" <gmx@ross.cx>
To:        freebsd-questions@freebsd.org, "Will Parsons" <varro@nodomain.invalid>, gyliamos@gmail.com
Subject:   Re: ssh + su problem
Message-ID:  <op.xgycecs1g7njmm@michael-think>
In-Reply-To: <slrnlousu1.1jd.varro@anukis.local>
References:  <slrnlokc4u.2it.varro@anukis.local> <20140601231728.9decb4f8b733c26bf040f963@yahoo.es> <slrnlosgkh.2le.varro@anukis.local> <20140604061922.GA2130@La-Habana> <slrnlousu1.1jd.varro@anukis.local>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 04 Jun 2014 21:30:09 +0200, Will Parsons <varro@nodomain.invalid=
>  =

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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.xgycecs1g7njmm>