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:date:from:to:cc:subject:in-reply-to:message-id
	:references:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=kGmHjJgsjozTFIs+nJTpNqx31MahpwFPm8aoiAw/MPA
	zm7KdIdBpV5NDfdhYaoN81mzbzjGyFTckOtAf+OJM3ZxASAjKytRupkNIOMh7Hdb
	mC+dJNXCY7+/i159Yr8W1K8C4t51U7gY7DKViHPn5x1yEFpVMfl8mGBJhrmD7NhA
	=
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:date:from:to:cc:subject:in-reply-to:message-id
	:references:mime-version:content-type:content-transfer-encoding;
	 s=default; bh=+9hhYpKLjbfWUqZuYM6mSEhLMjk=; b=pKo/E4Z0BFAt3B1sU
	AT8x+TaHjAGqaCxtzn/NV29n0UKkImYhuSS5W8NyZmQzc72eoBnj5dmYmou/hO6j
	H0JZelFvVeYRYPqE1+u4pqasZYMyNK3G/EVT1eLCOhgmp8U7tr2yPLJFKzheCMcv
	8O5Dud5XZw5amZ89iKbLMzqda4=
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
X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD autolearn=ham version=3.3.2
Date: Wed, 21 Aug 2013 12:42:32 +0200 (CEST)
From: Thorsten Glaser <t DOT glaser AT tarent DOT de>
To: cygwin AT cygwin DOT com
cc: s DOT gerhards AT tarent DOT de
Subject: Re: cygwin sshd dumping stack trace when not allocating pseudo-tty
In-Reply-To: <52138A66.3050406@cygwin.com>
Message-ID: <alpine.DEB.2.10.1308211235560.31430@tglase.lan.tarent.de>
References: <alpine DOT DEB DOT 2 DOT 10 DOT 1308191353590 DOT 23189 AT tglase DOT lan DOT tarent DOT de> <52123502 DOT 6070301 AT cygwin DOT com> <alpine DOT DEB DOT 2 DOT 10 DOT 1308201021500 DOT 6396 AT tglase DOT lan DOT tarent DOT de> <52138A66 DOT 3050406 AT cygwin DOT com>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by delorie.com id r7LAgohf014216

On Tue, 20 Aug 2013, Larry Hall (Cygwin) wrote:

> On 8/20/2013 4:32 AM, Thorsten Glaser wrote:
> > On Mon, 19 Aug 2013, Larry Hall (Cygwin) wrote:
> > 
> > > and to understand the method you're using to login.
> > 
> > SSH public-key auth, that is, RSA keys. (This is a requirement
> > because the process will run as batch job so we cannot use any
> > interactive auth method.)
> 
> Understood but method 2 and 3 allow for this as well.  They use a
> very different way of "getting there".  One of these two methods
> could work for you.

Hm. I must admit I’m a bit confused here, but AIUI if there’s a
problem with logging in (the auth method or that the home directory
is on the domain controller), then I should be unable to login with
SSH key, without password, interactively, too – right?

As things stands:

ssh-key interactive ⇒ works
password interactive ⇒ works
ssh-key batch ⇒ doesn’t work (-T, running a command, scp, rsync)
password batch ⇒ works

> It's telling you that cmd.exe doesn't understand UNC paths.  And that
> actually gives me an idea.  Can you create a local home directory

Hmm. When I login using ssh-key interactively, I get this:

tglase AT tglase:~ $ ssh cygbox
Last login: Tue Aug 20 10:21:46 2013 from tglase.lan.tarent.de
tglase AT cygbox:~$ pwd
//dc/tglase

So why would it work interactively but not in batch mode?

> and run ssh-user-config again to see if that helps?  If so, you can
> either continue to use this configuration or try method 3.
> 
> Other things I noted:
> 
>   1. You're running cygwin 1.7.9.  The current version is 1.7.24.  You
>      should upgrade.

I cannot “just” change things like this on the system unless
it’s known that not doing so fixes a problem (actually, the
system isn’t even normally mine to administer, I’m just helping
out).

>   2. Your CYGWIN environment variable contains "sshd".  You should
>      remove this.

I’ve got no idea where this is set; running a cygwin or CMD.EXE
doesn’t set $CYGWIN or %CYGWIN%, respectively, at all.

>   3. You have an orphaned installation at the level of your C drive.
>      If you have not already, you should remove this installation.

No, there’s precisely one Cygwin installation on that system,
which lives in C:\CYGWIN – I checked (even looked for stray
cygwin1.dll in e.g. windows\system32).

Thanks,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-314
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Boris Esser, Sebastian Mancke

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