X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-4.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<495F9091.9060305@cwilson.fastmail.fm>
Date:	Sat, 03 Jan 2009 11:21:37 -0500
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.19) Gecko/20081209 Thunderbird/2.0.0.19 Mnenhy/0.7.5.666
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Openssh compatibility problem?
References:	<gjei0c$l4o$1 AT ger DOT gmane DOT org> <495F8758 DOT 9000002 AT makuch DOT org>
In-Reply-To:	<495F8758.9000002@makuch.org>
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

Michael Makuch wrote:
> This is not a compatibility problem between cygwin/openssh versions. I
> am now seeing the problem just trying to ssh from plum to plum (an XP
> box). It seems that openssh 5.1 on cygwin is loaded with problems.
> 
> Anyone have it working? Anyone able to get it working without problems?
> 

Works fine here. It appears that the issue is the configuration on
plum's server. Some things to check:

1) make sure that you have opened port 22/tcp in plum's firewall

2) make sure that /etc/hosts.allow includes the line 'sshd : ALL' (or
'sshd : ALL : allow'

3) for localhost testing (e.g 'ssh localhost' on plum) add the following
to /etc/hosts.allow *before* 'all : PARANOID : deny'

'all : localhost 127.0.0.1 : allow'

or 'all : localhost 127.0.0.1 [::1] : allow' if you're using cygwin-1.7.

4) You might consider installing the syslogd or syslog-ng service on
plum.  Shut down sshd, run 'syslog-config' or 'syslog-ng-config', then
'cygrunsrv -S syslogd' or 'cygrunsrv -S syslog-ng'.  THEN restart sshd.

Now, you can try to ssh to plum, and tcp_wrapper errors will be reported
to plum's /var/log/messages, as well as some other sshd errors.

--
Chuck

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -