Am Sonntag, den 06.02.2005, 21:42 -0600 schrieb Marc Williams:
> On Sun, 06 Feb 2005 23:56:52 +0000, James Wilkinson wrote:
>
> > Marc Williams wrote:
> >> I've just started exploring the Expect language and have quickly hit a
> >> little bit of a speed bump. But I'm not sure it's Expect that's the
> >> problem.
> >>
> >> In an FC3 gnome-terminal, I try to run the following script:
> >> ----------------------
> >> #!/usr/bin/expect --
> >> spawn ssh 192.168.0.9
> >> expect "word: "
> >> send "password\r"
> >> expect "]$ "
> >> interact
> >
The Question is, why do you _NOT_ use ssh keys for authentication.
It's even more secure and there is no plaintext shell script with a
password hanging around in your filesystem.
man ssh-keygen should help you.
> > Do I assume that you're trying to do stuff this way in order to experiment
> > with Expect?
> >
>
> That assumption is correct. But everyone has to start somewhere and I am
> starting small with my home network and SSH/telnet. The more complex
> scripting needs of the servers at my work, of which there are many, will
> come later when I've got a handle on Expect. For now, If you've got any
> possibilities of solutions to this issue, please advise. Thanks!
>
--
Stefan Held VI has only 2 Modes:
obi@xxxxxxxxxxxxx The first one is for beeping all the time,
IRCNet: Obi_Wan the second destroys the text.
---------------------------------------------------------------------------
perl -e'map{print pack c,($|++?1:13)+ord,select$,,$,,$,,$|}split//,ESEL.$/'
---------------------------------------------------------------------------
GPG-Keyprint = EAF2 6A65 D102 F2DB 4970 2A67 455B 98F2 572C 3FA9
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
