Hi Jean, I just seen on git that you have begin to work on securing communications using SSL.
My question : will the SSL be used only to encrypt communications, or also to make some authentication between daemons to secure the infrastructure ? Because I've made some experiments today and actually a third-party malveillant arbiter can send to all accessible schedulers a fake Nagios config, making it (its pollers in fact) execute arbitrary commands instead of normal nagios checks. I'm also pretty sure other tricks can actually be done. Naturally, these arbitrary commands will be executed as the shinken user, not as root, but this user can still for example use the wget command to download an exploit for gaining root access... In the same way, imho, securing the livestatus module socket should be thought about (for example limiting hosts/IP that can send requests), against malveillant users that could send external commands or malformed requests (DoS). Furthermore, it's well-known that supervision servers have usually a wide access to local networks and servers... Regards, Laurent ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
