X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=At
	7sODrE0pQav5swDU883D+c08jFIgj9whGjOHdiiC9Mlglxn0WBN2nHFJi8bi7NeV
	cI4//82gRHf8GZ6aDmWXmibRi/TZux5H8b0WIADNkfCaNGehx9d4dEzpm61/KjMu
	1ojeQ077QkN+W+viU2wHpqdFcx6Z/KgiL3kHRxHs4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=2/VTd3Ig
	kViCiA6pEyraM6v2COg=; b=AytOKkKPJJQf/dEUl12YNiKgv29YEjUegm2FFj6O
	vI5Cc71F9wvgtiXDBC9l4Mu9Uw/Bxb2V+fjyMwbPta21g3Z11AhHNCmfzqEJ8gGH
	6J6BJKSbWoz6GUMNV5TdsFcO+rrKCkrOK4tgsa95he6jJF/BPlnxiEZruillBtGU
	ZzI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=2.4 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-qc0-f173.google.com
MIME-Version: 1.0
X-Received: by 10.140.39.164 with SMTP id v33mr889238qgv.80.1431033587275; Thu, 07 May 2015 14:19:47 -0700 (PDT)
In-Reply-To: <loom.20150507T085653-79@post.gmane.org>
References: <loom DOT 20150507T085653-79 AT post DOT gmane DOT org>
Date: Thu, 7 May 2015 15:19:47 -0600
Message-ID: <CANnLRdhFETB0boh4MXF--+v0=aC99=fKRTzX9gcVBN2ts3RTNA@mail.gmail.com>
Subject: Re: Strange SSH behaviour after updating to Cygwin 2.0.1
From: Stephen John Smoogen <smooge AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes

On 7 May 2015 at 01:15, Achim Gratz <Stromeko AT nexgo DOT 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 AT 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 AT 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