DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=kx3quWP+IYzg5ViVd7mWn0IvV++JxOzI+y6/AYtGRa/
	Sq/xFtLiZEisZAtsxlyaPiq6tOpogtnGW6LZFeRyEmtxkWX9DDowUQBqGGvxHySu
	9NVn/pE5qetXzu7klzsPiB0aofCAMe2v6ssTfhKZqUFc7Y1mW/hjKZeo5Evj6cLI
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 15 May 2015 18:41:00 +0900
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Strange SSH behaviour after updating to Cygwin 2.0.1
Message-Id: <20150515184100.2c2590c9b1b49b3d8617f334@nifty.ne.jp>
In-Reply-To: <87siazei6h.fsf@Rainer.invalid>
References: <loom.20150507T085653-79@post.gmane.org>	<CANnLRdhFETB0boh4MXF--+v0=aC99=fKRTzX9gcVBN2ts3RTNA@mail.gmail.com>	<87siazei6h.fsf@Rainer.invalid>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 14 May 2015 09:23:34 +0200
Achim Gratz wrote:

> That I already knew, and it's indeed fixed by making tcsh your default
> shell over on Cygwin.  I can't do that in the case I mentioned since I
> still haven't been able to convince our AD administrators to fill the
> respective fields.

Try: ssh -t user@hostname -- tcsh -l

With option -t, it should work as you expected.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

--
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