I have a small test Nagios 3.2 environment on a Suse platform ( 11 & 10 boxes 
)and was wondering about the encryption methods used.

I am working fine with no encryption configured on host or central server. I am 
getting all of the checks on the console.  Once I set it to any value other 
than 0 on both the server & host, I no longer get anything on the central 
server.  I've tried using the simple XOR and 3DES & DES

If I send a test job from the command line as per the instructions, with no 
encryption set ( not even simple XOR ) I see the reply in the nagios.log file 
on the Nagios server.  If I set the encryption on both & send the test job 
again,( restarting nagios on both)  it says 1 packet was sent successfully but 
nothing shows up on the central server.

I am still learning my way thru Suse & Nagios so not sure if the encryption 
process is part of the send_nsca or Suse.  I don't know what encryption is 
installed on the suse boxes or even how to check.

Is there a way to test or check what encryption(s) are installed on the boxes?

Since this is ultimately a totally private network, can I use the value of 0 
for no encryption ?  I know the cfg file explicitly says its not recommended

Sorry for the  stupid questions, but Nagios will do alot for my environment if 
I can get it squared away.

Thanks for your time.
                                          
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Nagios-users mailing list
Nagios-users@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

Reply via email to