You can do the automated stuff using scp
(or sftp) to your system as they use the same ssh setup. The most appropriate
way to do this would be get the public key from your server that you’re
pushing the software out from and putting it in the authorized keys file on the
servers where you’re pushing to. This way it doesn’t prompt for a
password at all.
Obviously you need to restrict who has
access to the account you’re pushing out from on the first server. I’ve
been in more than one place where we created a “security server” so
that only the admins had access to it and it was where we would push things out
from.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Kevin Whittaker
Sent: Monday, August 27, 2007 1:34
PM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Different
Ways to Install Client Software
All,
Ok,
I am starting to run into annoying problems. I used to install my new
clients using rcp. Well my company started disabling rsh on all server
(rightfully so).
Well,
I modified the install_client_software script and replaced the rcp,rsh with
scp, ssh and it worked great! I also would use ftp to install the client
when necessary.
Well,
now they are turning off ftp on all servers. For some reason, the ssh
install that used to work, no longer does?!?! I can ssh to the servers by
hand, but not using the script.
Anyway,
my question is what other ways are there to install the client software on a
Solaris 8/9/10 box? Or a Linux server?
Kevin
Whittaker
Syniverse
Technologies
Systems
Engineer - UNIX Admin
