Nagios Support Forum

Refeering to this post
http://serverfault.com/questions/664390 ... ion-issues

Michael Medin wrote:If you are using 0.4.3 (which I assume) "default" security has been improved a bit. This unfortunately means the rather insecure check_nrpe wont work.
When you install NSClient++ you have the option of selecting "insecure mode" which should work fine with the classic check_nrpe.
You can also tweak this "in post" using the nrpe command like so:
nscp nrpe install --insecure

If you want to use the "slightly more secure" modes offered by NSClient++ you need to install NSClient++ on the nagios server as well and use the NSClient++ version of check_nrpe which support modern SSL and certificate based authentication.

What does the statement "you need to install NSClient++ on the nagios server and use the NSClient++ version of check_nrpe which support modern SSL and certificate based authentication" referring to? Please advice.

Thanks

Bearing in mind that the linked article is somewhat old, I believe Michael Medin (the NSClient author) was saying that in order to get a version of check_nrpe that will work with NSClient using "slightly more secure" methods, you will need to use the version included with NSClient.

We have since made changes to NRPE and check_nrpe to allow for far more secure encryption, so I don't believe this is still necessary.

tmcdonald wrote:Bearing in mind that the linked article is somewhat old, I believe Michael Medin (the NSClient author) was saying that in order to get a version of check_nrpe that will work with NSClient using "slightly more secure" methods, you will need to use the version included with NSClient.

We have since made changes to NRPE and check_nrpe to allow for far more secure encryption, so I don't believe this is still necessary.

Which version of nrpe & check_nrpe are you referring to?

The developer has a linux version of NSClient++ available, and in that version he has a plugin like check_nrpe called nscp that works with other machines running NSClient++.

I dabbled with this some time ago:
http://sites.box293.com/nagios/guides/n ... t-from-rpm

However it requires you to install the full NSClient++ on the linux machine just to the nscp command
The recent versions of NSClient++ are backwards compatible with check_nrpe, they just need you to run these commands:

Open a command prompt
Type cd "\Program Files\NSClient++\" and press Enter
Type nscp settings --path /settings/NRPE/server --key insecure --set true and press Enter
Then restart the NSClient++ service.

More information here:
http://sites.box293.com/nagios/guides/n ... t-ini-file

I'm currently doing testing on the beta version of NRPE 3, it is adding in advanced security so hopefully we won't see to use the "insecure" mode.

https://github.com/NagiosEnterprises/nr ... DME.SSL.md

Box293 wrote:The developer has a linux version of NSClient++ available, and in that version he has a plugin like check_nrpe called nscp that works with other machines running NSClient++.

I dabbled with this some time ago:
http://sites.box293.com/nagios/guides/n ... t-from-rpm

However it requires you to install the full NSClient++ on the linux machine just to the nscp command

Code: Select all

/usr/sbin/nscp nrpe host=win2008r2-01

The recent versions of NSClient++ are backwards compatible with check_nrpe, they just need you to run these commands:

Open a command prompt
Type cd "\Program Files\NSClient++\" and press Enter
Type nscp settings --path /settings/NRPE/server --key insecure --set true and press Enter
Then restart the NSClient++ service.

More information here:
http://sites.box293.com/nagios/guides/n ... t-ini-file

I'm currently doing testing on the beta version of NRPE 3, it is adding in advanced security so hopefully we won't see to use the "insecure" mode.

https://github.com/NagiosEnterprises/nr ... DME.SSL.md

Thanks Troy, all the info I needed.

@rajasegar, Is it all right if we lock this topic and mark it as resolved?

mcapra wrote:@rajasegar, Is it all right if we lock this topic and mark it as resolved?

Ok. Please close it.