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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=QR9ts18jBt5l0rGJAZcNTJ0lYouH2jxDJ1cDOhCVFSA
	/CPstIelDPfIdOsKnWxK1X8MW28u89vflUNy5bjXt0EIfxC9KCB45kclMClwAjPD
	Z3mo5wIZsv2Fhh3sM7cI43iLZC0IINQFGRBMK3AcUyUbGgKx89hgM1NuHPBQDZMs
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=GI2nmThe0NNOwvbVYW0CLtx5inM=; b=LIRTAMuEWy1KYLrnC
	sbiHXF2YE68Ri3KA4zeT+MJm7Z7eQ/Gey31zSX6+7G1BPIYBaFx0AbRHxb2NQWKB
	L9fb951od50oHcMMWbXWktjWVVlEh74g6viNpZ5bACl5iw2v4nv+ma71cm5lKKip
	V3SLLtGOBfYYSLzWjL8WQOOWTI=
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=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO:	limerock04.mail.cornell.edu
X-CornellRouted:	This message has been Routed already.
Message-ID:	<5329C9EF.1000305@cornell.edu>
Date:	Wed, 19 Mar 2014 12:46:39 -0400
From:	Ken Brown <kbrown AT cornell DOT edu>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Public key authorization problem with latest snapshot
References:	<5329B9D0 DOT 6070703 AT cornell DOT edu> <20140319160914 DOT GD2715 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20140319160914.GD2715@calimero.vinschen.de>
X-IsSubscribed:	yes

On 3/19/2014 12:09 PM, Corinna Vinschen wrote:
> On Mar 19 11:37, Ken Brown wrote:
>> Here's some more weirdness involving the recent changes to exception
>> handling on 64-bit Cygwin.
>>
>> I have an ordinary user kbrown and an administrator user
>> kbrown-admin. I use the following command to simulate "su":
>>
>>    ssh kbrown-admin@$(hostname) .
>>
>> With the current (2014-03-18) x86_64 snapshot, this doesn't work if
>> I try to use public key authorization.  I simply get a message
>>
>>    Connection closed by fe80::81db:bf3a:6434:6015%11
>>
>> and I'm not even prompted for my passphrase [*].  But if I move my
>> id_rsa and id_rsa.pub out of the way, I'm prompted for a password,
>> and I can login successfully.
>>
>> Reverting to the 2014-03-17 snapshot fixes the problem.
>
> I just checked in a change.  Please give it a try.  If this doesn't work
> either, I don't know how to proceed.

This fixes the public key authorization problem, but the timeout during 
the starting of gtk applications is back.  The "window-default" program 
from the other thread is still a test case for that problem.

Ken


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

- Raw text -