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=Nh
	KpzyEfS6+24uAxTwQUcPIvca8W6UwFD78FhpElJWj86V1SRI5lhQSwyXiqrFXnnV
	YuAsv1PcYWo/8ETEP/07lwPfzbpW4SvzQa6SSwKATiUYMZbYjKQ1pzelSaDtyqYe
	KoNKkd3jbckRDlwMKeo106i9BHE2VmpX3RMoq8tl8=
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=EOl8Q+3I
	OmnGxXP1qBzbKjsaqKs=; b=aA1CQtGKKSp7WvED311d+myEv3py0xWjVE9hAQlC
	10z5nCq4oCVjZ/tccFM/ANM3jlPakHrHLD1b0bRCdyM8jAhBxMm46oVGv/5thEGQ
	zq5bS4fAW/wFifvtGgNRU/MJdEzMyhUFWMirJRrsLDqz+Wlx8MV5SlVCUbc009bD
	ajg=
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=0.9 required=5.0 tests=AWL,BAYES_20,FREEMAIL_FROM,KHOP_THREADED,NO_RELAYS autolearn=ham version=3.3.2
X-HELO:	mail-ve0-f180.google.com
MIME-Version:	1.0
X-Received:	by 10.52.98.131 with SMTP id ei3mr23566420vdb.4.1379353655444; Mon, 16 Sep 2013 10:47:35 -0700 (PDT)
In-Reply-To:	<5237373E.1070905@cygwin.com>
References:	<CAMhuX2BzMOmeLeJSUcsm8yMd4gw8THBiBG=+iorVgv1uDwveJQ AT mail DOT gmail DOT com> <CAMhuX2BoDhcVUyv_ba4jXC+Y0fX=Fa50OOFfzK_fBBQe9N=o-A AT mail DOT gmail DOT com> <5237373E DOT 1070905 AT cygwin DOT com>
Date:	Mon, 16 Sep 2013 13:47:35 -0400
Message-ID:	<CAMhuX2ALMEw+2D5_urYo_MPhbjvebROs5UAY4L0Gx1a0rAagSA@mail.gmail.com>
Subject:	Re: Fwd: Way to test cyglsa?
From:	Evan Rowley <rowley DOT evan AT gmail DOT com>
To:	Andrey Repin <cygwin AT cygwin DOT com>
X-IsSubscribed:	yes

Thanks for the recommendaitons Larry.

If $USER is the test, then it appears cyglsa is working on this machine.

The firewall is disabled.

Thanks for refering me to the BLODA. I noticed some Symantec products
listed there. Symantec's Endpoint Protection and Symantec's Bakcup
Exec are installed on this server. I doubt those are causes because
the same programs are installed on another server where sshd works. In
fact, that other server is a copy of this server in question AKA the
one which isn't working. The copy was made a few years ago so there
are minor differences between the two machines. During my testing I've
used the same sshd configurations on both and I can't for the life of
me figure out why one works while the other doesn't.

For a while, I thought there was an issue with user switching but
event log shows success for cyg_server and even for the users I
attempt to login with via ssh.

Still, sshd appears to close after ssh sends a publickey packet.

These servers sit on a domain with a 'strong password' requirement.
I'm wondering if there are special keyboard characters in the
passwords which may interfere with the way cygwin handles user
authentication.

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