Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
From: "Erdely, Michael" <mike AT erdelynet DOT com>
To: "cygwin" <cygwin AT sources DOT redhat DOT com>
Cc: "SSH List" <ssh-l AT erdelynet DOT com>
Subject: Problems with OpenSSH 2.3.0 (was RE: SSHD as a Service)
Date: Thu, 16 Nov 2000 09:55:58 -0500
Message-ID: <HLEFLHBNJIAFNBEFLEANAEEDCFAA.mike@erdelynet.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
In-Reply-To: <3A139D3D.8BBCF2CD@redhat.com>

Both a friend of mine and I are experiencing the same problem.
Running on Windows 2000 Pro (and he might even be using server).

I read the readme.  I went into more detail at
http://mike.erdelynet.com/sshd.asp and I followed that set up exactly.

The problem I'm having is: when I'd run "ssh -v localhost", I'd get "bad
packet length" and get disconnected.  It would even stop the inetd service
on the server.
Inetd is running as the SYSTEM account and system.system owns /etc/ssh*.
/etc/ssh_host_key and /etc/ssh_host_dsa_key had only 600 permissions.

The sshd_config had these lines in it:
Protocol 2
HostKey /etc/sshd_host_key
RSAAuthentication no
PasswordAuthentication yes

Here's a weird part: I stopped Inetd.  I installed SRVANY as a service
("SSHD") using SRVINSTW.  I added the appropriate Parameters key in the
registry to call "C:\Cygwin\usr\sbin\sshd.exe" and started the service.  It
worked like a charm.  My main purpose for doing that was, expecting it to
fail, the first few times I ran it, I had the service interact with the
desktop and I used the "-d" switch on the service (since I can't figure out
how to do that with inetd).  But it worked.  No problems at all.

So, I deleted all of the files in the openssh-2.3.0p1.tar.gz package and
installed openssh-2.2.0p1.tar.gz from
ftp://ftp.freesoftware.com/pub/sourceware/cygwin/latest/openssh/ and
everything works beautifully.

Especially based on the security advisory on Bugtraq about OpenSSH versions
prior to openssh-2.3.0p1, I'd like to get openssh-2.3.0p1 working again.

Ideas,
Mike Erdely
mailto:mike AT erdelynet DOT com
http://mike.erdelynet.com/

-----Original Message-----
From: cygwin-owner AT sources DOT redhat DOT com
[mailto:cygwin-owner AT sources DOT redhat DOT com]On Behalf Of Corinna Vinschen
Sent: Thursday, November 16, 2000 3:39 AM
To: cygwin
Subject: Re: SSHD as a Service


"Erdely, Michael" wrote:
>
> Well, you can use VanDyke's VShell.  I haven't played with it (yet), but
it
> might be what you're looking for.
>
> On the other hand, I've had great success with OpenSSH 2.2.0.  But, lately
> I've been having some problems with OpenSSH 2.3.0.

What problems do you have? Did you read the README? There's a hint about
a change in handling the file permissions.

Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                        mailto:cygwin AT sources DOT redhat DOT com
Red Hat, Inc.
mailto:vinschen AT redhat DOT com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com