Searchd kaltura-sphinx listening to the world

Currently I change one setting after each update of the kaltura backend:
The searchd is defined listening like this:

searchd
{
listen = 0.0.0.0:9312:mysql41

But I only need him listening to localhost, so I change that line and restart the service.

searchd
{
listen = 127.0.0.1:9312:mysql41

Your sure can hide that service using firewall settings, but why listening to any interface in the first place? At least I expect that installation on a stand alone server running all processes.

Hi @kaikretschmann_1,

It is certainly fine to make this change. I won’t be making it in the vanilla configuration because as you know, Kaltura can be installed in many ways with different role[s] per node and so, since the same config file is used in all cases, it should remain this way by default. Indeed, for a standalone server, there is no need for Sphinx to listen on anything but the loopback I/F [127.0.0.1] and hardening is always a good idea:)