Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <39DBA588.10B7053E@cygnus.com> Date: Wed, 04 Oct 2000 23:47:52 +0200 From: Corinna Vinschen Reply-To: cygwin X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-SMP i686) X-Accept-Language: de, en MIME-Version: 1.0 To: cygwin Subject: Re: Open SSHD References: <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001004140931 DOT 00aeb100 AT imap DOT coe DOT utah DOT edu> <02c101c02e41$82b97cc0$73191eac AT neptune> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Please note that OpenSSH and OpenSSL packages are officially part of the base distro since 26-9-2000, announced on 27-9-2000: http://sources.redhat.com/ml/cygwin/2000-09/msg00915.html The Cygwin setup did downloaded them since that date as well. I don't understand the problem here. I have described the installation in detail in the README file `/usr/doc/Cygwin/openssh-2.2.0p1.README'. For the beginning it will be helpful to start the script `/usr/bin/ssh-config' which creates the necessary configuration and key files. Both files were already part of the original distribution on ftp.franken.de and their existence was announced more than once in this forum. "Erdely, Michael" wrote: > > Along those lines, I wrote up a web page with my steps to getting it work: > http://mike.erdelynet.com/sshd.htm. > [...] > ----- Original Message ----- > From: "Bret Jordan" > > [...] > > copied sshd.exe to c:\local\sbin\sshd\sshd.exe > > copied ssh-keygen.exe to c:\local\sbin\sshd\ssh-keygen.exe Don't use Windows paths. Your description is ok if the installation root is C:\ but this is not the default installation. Your description would be valid in all environments when using POSIX paths like copied ssh-keygen.exe to /local/sbin/sshd > > run c:\local\sbin\sshd\ssh-keygen -d -b 1024 -f c:\etc\sshd_host_dsa_key > > > > NOTE: I was unalble to get it to work with a passphrase other than > > . I will keep working on this, or maybe someone knows how to make > > this part work. This is correct behaviour. As it's even mentioned in the ssh-keygen man pages the host key must have an empty passphrase. > > The passwd file looks like > > someusername::1:10:User Name:/home/someusername:/winnt/system32/cmd.exe Where did you get the uid/gid? They are not related to the id's which are given by NT. So you didn't use mkpasswd/mkgroup for creating your /etc/passwd and /etc/group files. It's called by the Cygwin setup in the postinstall. If you didn't use setup.exe, call them by yourself. > > I can make a connection to a nt box running opensshd. I can run most all > > dos/nt commands. I can even run most all of the bin utils. The problem > > come around when I try to run a program that is a command character > program > > (edit, vi, emacs -nw, pmon, etc). When I try to run these programs it > just > > causes the connection to hang. When you run vi it causes the connection > to > > [...] > > Question: > > Can you, and if so, how do you run command character programs through the > > ssh connection? Is there some sort of ENV variable I need to set? I already answered your question yesterday: http://sources.redhat.com/ml/cygwin/2000-10/msg00067.html 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 cygnus DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com