Re: Strange SSH behaviour after updating to Cygwin 2.0.1

[Stephen John Smoogen <smooge at gmail dot com>]

On 7 May 2015 at 01:15, Achim Gratz <Stromeko@nexgo.de> wrote:
> I'm seeing strange behaviour from SSH after updating both sides to Cygwin
> 2.0.1.  The symptoms, logging in via a 32bit client into a 32bit or 64bit
> sshd instance on the server:
>

I have replicated this using Cygwin ssh to a Linux server. However I
also replicated it using Linux -> Linux

[smooge@seiji ~]$ ssh xanadu -- tcsh -l
X11 forwarding request failed on channel 0
Warning: no access to tty (Bad file descriptor).
Thus no job control in this shell.
^CKilled by signal 2.
[smooge@seiji ~]$ uname -a
Linux seiji.int.smoogespace.com 3.10.0-229.1.2.el7.x86_64 #1 SMP Fri
Mar 27 03:04:26 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

So it might be a 'works as it is supposed to now' even if it is not
the same behaviour as before. Doing a bunch of google hunting.. pretty
much all the places it comes up with are "set your shell to tcsh by
default so the tty is setup by login" or "use bash then go into tcsh".

The Cygwin client I duplicated in on was
CYGWIN_NT-6.1 smooge-PC 2.0.0(0.287/5/3) 2015-04-27 15:30 x86_64 Cygwin


-- 
Stephen J Smoogen.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple