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:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=vX8g1yhmSGKxdW1k
	qtk4O2+Q7vKt7JVbzc7vqWewhdvot+wbNEfMhcLIxJgBXw8mxe4wdw/hPxjIzrch
	K/9VlLHO5IGOwQfJVxpGmW9rOdn4Ko62og/x9eN0YE1u3fp2+wfsLgABWaKUCKf7
	kch+fKhqg19pHcJqeLHtFLtPCIw=
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:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=DDaIBU6ejmfO7qb1bY4zLV
	UrYq8=; b=JWM3c9M/i2r4uibTJtJZMsaDGuUZuCpMOq8Zhi/bGw+Vr1o/suyFzH
	5aOD8f2MX+14Nuq9BYpppoY8Lhzz7omKRDz3vYIvuwlqOPz1h+du0NniephtBbte
	bircIZXv2j1/vl1lLS3Tpy2cuyC8NcD6egt1dh9Ih7y87IdRXpamc=
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.2 required=5.0 tests=AWL,BAYES_50,BOTNET,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RDNS_NONE autolearn=no version=3.3.1
Message-id:	<51F2EA4A.6060107@cygwin.com>
Date:	Fri, 26 Jul 2013 17:29:46 -0400
From:	"Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Cannot build debug/-Zi using VS 2010 SP1 via ssh with public key auth from local administrator account
References:	<C511312E-7990-4D2B-8751-0824C26D98B8 AT basissw DOT com> <51F2B2A9 DOT 2060607 AT cygwin DOT com> <A55E8DE6-5C7D-465F-AB97-45E398ADF63C AT basissw DOT com> <EA06E433-3764-4D04-93E9-E1E57FC5A93F AT basissw DOT com>
In-reply-to:	<EA06E433-3764-4D04-93E9-E1E57FC5A93F@basissw.com>

On 7/26/2013 4:22 PM, J. P. Abelanet wrote:
>
> On Jul 26, 2013, at 12:51 PM, J. P. Abelanet <jp AT basissw DOT com> wrote:
>
>>
>>>
>>>> I've since tried the following:
>>>> - running ssh-host-config on (a) and rebooting, with no effect
>>>> - completely removing CYGWIN and all traces of sshd
>>>> (http://cygwin.wikia.com/wiki/Uninstalling_Cygwin) and reinstalling on
>>>> (a), with no effect
>>>
>>> We discourage people from following Cygwin advice from ad-hoc sites.  In
>>> this case, it provides a synopsis of how to do this and then points to a
>>> link in the Cygwin FAQ from where the synopsis came.  Two things should
>>> make anyone think twice about the information at this site:
>>>
>>> 1. It points to the Cygwin FAQ as the source.
>>> 2. The link to the Cygwin FAQ is broken.
>>
>> Thanks for the warning - I'll try to be more diligent in the future.
>>
>>>
>>>> - completely removing VS 2010 and all related packages (I think), and
>>>> trying to build using the untouched version of VS 2008 I had previously been
>>>> using, and now building debug across CYGWIN/ssh/pub key with VS 2008 fails
>>>> as well
>>>
>>> Yeah, that of course assumes that the uninstall undid all that the install
>>> did.  There's not a good way to verify that.  If you can narrow down the
>>> time-frame (with the Cygwin Time Machine for example - Google it) when you
>>> see the problem appear, that could help find a solution, assuming you're
>>> still seeing the problem with 1.7.22.
>>>
>>
>> Understood.  And yes, the problem still occurs with 1.7.22.
>>
>> As I mentioned originally, I'm using a local (non-domain) account,
>> and it has administrator privileges.  What is the fundamental difference between
>> public key authentication and password authentication in this context?
>>
>
> Here is the source of the problem, and I'm virtually certain that these problems occurred
> as a result of running setup.exe on the two machines as part of the upgrade
> (note that I did not, for various reasons, run setup.exe on the two machines that still work).
> Here are the USER* variables on machines (a) and (b), the two problem machines,
> when logging in via ssh/pub key:

How did you install?  Did you pick "Just For Me" or "All Users".  The
latter is required for pubkey authentication.  You can also check if
password authentication resolves the problem.

If none of the solutions/suggestions/diagnostics offered so far resolve
the problem, may I suggest that you read and follow the problem reporting 
guidelines found at the link below with any follow-up?

<http://cygwin.com/problems.html>

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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