Skip to main content

Add a certificate when you build the NSClient++ and Centreon dependencies centreon_plugins.exe and check_logfiles.exe to be more compliant with the security solutions and practice.

  • Persona : As a Centreon administrator

  • Problem to solve : When you install the NSClient++ build by Centreon, as this build was not signed, the execution of the installation is more slow. When you browse the folder to configure the NSClient++ access is more slow, Same behavior when you just want deploy a more update centreon_plugins.exe and check_logfiles.exe

  • Expected outcome : Enhance the time of deployment of the NSClient++ and the centreon scripts centreon_plugins.exe and check_logfiles.exe. It’s a best security practice, who allowing to have the certitude to install a Centreon product.

  • Potential solutions : Adding certificate with your build process for all your executable with the NSClient++ build, it more compliant with the security practice, the security solution, and more enterprise compliant.

Regards

Updated idea statusNewIn Backlog

Updated idea statusIn BacklogDiscussion ongoing

Extra question:

Could a person building their own copy integrate their own cert?


Hi @hmorales 

 

Yes, there’s everything on the github repo to create your own certified windows executable. 


As we plan to replace NSClient++ with WSMan and maybe also Windows node exporters, we probably won’t make it a high priority unless it gets a lot of votes. 

 

Cheers


Updated idea statusDiscussion ongoingNeeds Votes


As we plan to replace NSClient++ with WSMan and maybe also Windows node exporters, we probably won’t make it a high priority unless it gets a lot of votes. 

 

Cheers

 

By this change with Windows Exporter we depreciate a lot of plugins/pack GitHub - prometheus-community/windows_exporter: Prometheus exporter for Windows machines

Could you give more information about this information or maybe the roadmap ?


Yes, we still plan to maintain NSCLient++ as it is, adding some features when relevant but we very likely invest much in having a more complete coverage of node exporter metrics. 

 

We keep WSMan capability to be able to run powershell on remote boxes when specific CmdLet might bring more information than node exporter does. 


No official roadmap, as soon as a user can deploy the windows node exporter with some additionnal module enabled, we will develop it to make it an official pack.

 

Best​​​​


Needs VotesDeclined