On Sat, May 13, 2006 at 07:21:35PM +0200, Uwe Hermann wrote: > any chance the bacula daemons (all of them) could listen to the local > loopback interface (i.e. 127.0.0.1) _only_ per default? Currently they > listen to _any_ (all) interfaces, which exposes them to the Internet > usually.
Hi Uwe, To actually have the daemons bind to a specific interface would require some new configuration file options. I would be happy to forward this to upstream if you would like, but would not want to maintain a local patch to achieve it. That said, Bacula is built with tcpwrappers (libwrap) support. While not exactly the same, do you think that libwrap may be an acceptable solution for this? There is an open bug (#360530) calling for documentation of the proper hosts.allow/deny configuration for Bacula already. I hope to get that documentation written soon. As far as what the defaults should be out of the box, I'm not really certain. Precedent among other packages is not entirely clear. Databases these days default to localhost only, while most other networkable services default to allowing network connections. I would be interested to hear feedback from some more people before changing the default. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
