SSH client/server comms - user/password, minimal key usage
Posted: Wed 30 May 2007 19:59
I want to create a common SSH server executable, installed as a service, on about 300 Win 2K servers. All of these servers are on our protected company WAN, so I'm concerned with encrypted data between machines (via SSH tunnel), but not so much about authentication between servers and client. A single client SSH machine will "talk" with all 300 servers, using a common password/user i.d.
As I want to automate the deployment/installation/startup of the SSH server executable/service on the 300 Win2k servers, I'd like to have a single encrypted user/key storage file to be deployed to all the servers, if possible.
Only one user/password will be in the storage file, i.e. the one the client SSH machine will use to authenticate with all the servers. What can I do to minimize the number of DIFFERENT keys I need to put in to the common (user/key) storage file ?
As I want to automate the deployment/installation/startup of the SSH server executable/service on the 300 Win2k servers, I'd like to have a single encrypted user/key storage file to be deployed to all the servers, if possible.
Only one user/password will be in the storage file, i.e. the one the client SSH machine will use to authenticate with all the servers. What can I do to minimize the number of DIFFERENT keys I need to put in to the common (user/key) storage file ?