Realistically, you really only need ssh.exe and cygwin1.dll to make ssh
connections with the Cygwin port of OpenSSH. You may get a few errors
about not being able to find the ~/.ssh directory and writing to the
known_hosts file, but with a few tweaks (creating a
C:\Cygwin\home\%username%, creating a C:\Cygwin\etc, creating a
C:\Cygwin\bin and putting cygwin1.dll and ssh.exe in there). You can
even create a c:\cygwin\etc\ssh_config to set up specific options for
your clients. You'd probably also want to add C:\cygwin\bin to the path
on each machine.
You could also attempt a minimal installation of Cygwin's setup and just
install things like openssh, openssl, binutils, fileutils, bash, ash and
others to have a minimal environment (ie: leaving out gcc, dejagnu,
ssmtp, ....).
Hope that helps,
-ME
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
Roeland Meyer
Sent: Tuesday, April 10, 2001 1:04 PM
To: SSH (E-mail 2)
Subject: CLS SSH 4 Win2K
We're setting up a CVS repository for Jbuilder4 Enterprise. We have our
Linux and Solaris environments working (the CVS repository lives on a
Linux box), but we are having problems with Win2K clients. In order for
":ext:[EMAIL PROTECTED]:subdir" to work we need a command line interface of
ssh. A straight port would be fine. I would really not want to have to
setup a gcc build environment (Cygwin) on every client and we have no VC
build environment (latest we have is MS-VC v5). Yes, we have MindTerm,
but that's not a CLI, only executable from CLI.
Can someone help?
--
ROELAND M.J. MEYER
Managing Director
Morgan Hill Software Company, Inc.
TEL: +001 925 373 3954
FAX: +001 925 373 9781
http://www.mhsc.com
mailto: [EMAIL PROTECTED]
