Using SSH in Shell Scripts

fotoguy · 04-07-2006, 09:16 PM

Ok understand now, unfortunately I don't know of anyway to autofeed a password.

/bin/bash · 04-08-2006, 05:47 AM

I think expect will do what you want.

GNUsavior · 04-21-2006, 07:17 PM

ok, i cheated slightly...but i have another question in doing so...towards the beginning of my script i decided to use the 'ssh-agent /bin/bash' command. This initially worked fine...my script would ask a few questions and then this would run along with the 'ssh-add' command it would ask me for my password once, leaving my key in cache and continuing. Now all of a sudden its constantly telling me it cant connect to my authentication manager. From what i understand this is because certain environemtn variables are not set, such as SSH_AUTH_SOCK. Here is the portion on how i had it:

Code:

# use ssh-agent to set up proper environment variables
echo ssh-agent /bin/bash
# add the current users key to cache and ask for password
ssh-add

I suspect when this working smoothly that maybe i had put in the command manually and it was still lingering. So apparantly this is wrong, what is right? The ssh-agent starts a sub-shell where the environment strings are stored there and not in the parent as i understand it. If i just go `ssh-agent /bin/bash` and such, nothing shows on the screen until i type 'exit'. How do i put this in my script and get the output and behavior i'm looking for? Thanks for the input.

GNUsavior · 04-24-2006, 10:31 AM

Any ideas anyone?

jiml8 · 04-24-2006, 09:30 PM

You need to get keychain in order to manage ssh-manager and make sure that every ssh process can pick up the proper ssh-manager session.
http://www.gentoo.org/proj/en/keychain/

Please note that keychain may want to put your session credentials in a subdirectory, then look for them in the main directory. I handled this with a symlink.

I am doing the exact same thing you are doing, remotely managing/reconfiguring linux machines via a scriptfrom a server. I question that you can't have scripts on your client machine and run them; seems to me that if you have SSH access you certainly can put a script on the client, run it, then delete it. This is what I do.

By doing it that way, I eliminate the problem you are having, of multiple password entries. I upload the script, run it sudo exactly once via SSH, and it gathers all data/does all work. I enter the password once. When I am all done, I delete the script.