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
Date:	Thu, 12 Apr 2001 12:41:40 -0400 (EDT)
From:	Antonio Bemfica <antonio AT axolotl DOT ic DOT gc DOT ca>
To:	SS <fully_technical AT yahoo DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: SSH, Expect & Cygwin
In-Reply-To:	<20010412154842.5452.qmail@web5101.mail.yahoo.com>
Message-ID:	<Pine.BSF.3.96.1010412123342.69106D-100000@axolotl.ic.gc.ca>
MIME-Version:	1.0

On Thu, 12 Apr 2001, SS wrote:

> However, I was suggested to try with an EMPTY PASSPHRASE, & that works
> fine from the command line as well as from the Expect script! the script
> is as below: 
> 
> #!/usr/bin/expect
> spawn /bin/ssh -l myusername -p myport myhostname.abc.com "ls -l"
> expect eof
> 
> But I dont want to do that because the whole idea od using SSH is lost
> if I am using an empty passphrase. 

Not really, I don't think. Authentication still takes place based on the
user's keys. This should be pretty secure as long as the location of the
keys is not world-readable (ssh will fail to work if it is, I think) and
the machine where you coming from has not been compromised. 

I use this method to run pre-backup scripts on NT and Unix hosts as user
operator (you don't need expect at all).


A.


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -