This is the mail archive of the
mailing list for the Cygwin project.
Re: Fwd: Way to test cyglsa?
- From: Evan Rowley <rowley dot evan at gmail dot com>
- To: Andrey Repin <cygwin at cygwin dot com>
- Date: Mon, 16 Sep 2013 13:47:35 -0400
- Subject: Re: Fwd: Way to test cyglsa?
- Authentication-results: sourceware.org; auth=none
- 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>
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
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple