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
X-Originating-IP: [64.81.32.14]
From: <want_2_learn_freebsd AT hotmail DOT com>
To: "Larry Ploetz" <Larry AT Stanford DOT edu>, <cygwin AT cygwin DOT com>
References: <3B952C78 DOT 3010301 AT Stanford DOT edu>
Subject: Re: sshd on Windows
Date: Tue, 4 Sep 2001 14:57:17 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Message-ID: <DAV45ydlb9rXg5wlSe900001d41@hotmail.com>
X-OriginalArrivalTime: 04 Sep 2001 21:58:03.0334 (UTC) FILETIME=[AB935E60:01C1358C]

http://www.networksimplicity.com/openssh/  <-- here is a simple solution.  I
use on all my windows servers.  Console Support sux, but to reload my dns
(on windows system but this will work on Unix too) I have a batchfile called
reload_ns1.bat like so:

@echo off
ssh superfreak AT ns1 DOT domain DOT com reload-dns.bat

And so that bat would log in, execute reload-dns.bat and exit.  If you just
want to get ssh on windows as a client get:
http://www.networksimplicity.com/openssh/  and install just the client.



----- Original Message -----
From: "Larry Ploetz" <Larry AT Stanford DOT edu>
To: <cygwin AT cygwin DOT com>
Sent: Tuesday, September 04, 2001 12:33 PM
Subject: sshd on Windows


> Forgive me if this is the wrong forum for this sort of question (and if
> so, if anyone knows a more appropriate one, I'd appreciate it!).
>
> We use ssh on Unix systems to run "batch" jobs using a horrible
> scheduling product that I won't name. The horrible scheduling product
> (which I'll refer to as HSP) is just a multi-system cron replacement,
> with the added attraction that if a job finished (e.g.) successfully,
> that will trigger a successor job (on any system the HSP is installed
> on). For systems that don't run that many jobs, rather than install the
> HSP on it, we run a job from a system the HSP is installed on to ssh to
> a system that it isn't installed on  to run the job. Something like:
>
> NodeA (HSP installed)
>     Job1: ssh -l userid NodeB somecommand
>
> Now they want to run a script in a job on a Windows system after some
> job on a Unix system finishes successfully, and which in turn may
> trigger a third job. I suggested looking into any secure way of
> triggering a script to be run on a Windows system as a particular userid
> (regardless of whether that userid is logged in (owns the display?) at
> the time the job is run) and getting some indication of success/failure,
> and they wanted to know if sshd is available on Windows.
>
> So my questions are:
>
> 1) Can I point the Windows administrators to a url for an sshd they can
> download and run w/out compiling? The cygwin DLL would be necessary?
> 2) What Windows would it run on? (Obviously one that supports multiple
> logins)
> 3) Is there documentation for it (e.g., how to set up a .shosts file for
> a given userid), or would they be asking lots of questions on this forum?
> 4) Would this sshd do what I'm suggesting they do?
>
> Many thanks in advance; any advice would be appreciated. Please cc my
> email address as I don't read this mailing list regularly.
>
> Thanks,
> - Larry
>
>
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/