check by ssh

[Neil]

C. Bensend writes: 

> No such beast, and I'm kind of happy about that. 
> 
> I think you're looking at the wrong idea - you don't have to run ssh-keygen
> on the client machines you're testing, you only need to make sure the nagios
> user's public key is distributed. 
> 
> SURELY with 100 different UNIX servers you have tools to automatically
> push files / config changes...  Use those tools to push a copy of
> authorized_keys2 to all the client machines, and yay, you're done. 
> 
> Hell something like this should work in a pinch (not tested, but should
> be a piece of cake to fix if it doesn't work): 
> 
> for foo in `cat server-list`; do
>    scp authorized_keys2 nagios@$foo:.ssh/
>    ssh nagios@$foo chmod 0600 .ssh/authorized_keys2
> done

I did get your idea but I guess, when creating keys, it's really tide in to 
a username on the remote ssh server. This is going to be one big hurdle too. 
I'd have to fill out a form for a access request so they can create a single 
user account on each of the servers I will request. 

But anyways, I'll just follow what you guys recommended. 

Thanks again. 

Neil


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null