HAH! I say hah! Greg Vickers wrote: > Hi all, > > I've found out that tcpwrappers were causing my authentication problems > (bconsole couldn't connect to the bacula-dir process.) > > If remove the 'ALL: ALL' line from hosts.deny bconsole will connect to the > director successfully. I reinstate the 'ALL: ALL' clause and the following > hosts.allow file will not allow bconsole to connect: > bacula-dir: ALL > bacula-fd: ALL > bacula-sd: ALL > > (I know I probably don't need the bacula-fd and -sd lines, but I included > them out of frustration.) > > What else should I include in my hosts.allow file to allow bconsole to > connect to the director?
According to http://www.bacula.org/dev-manual/Bacula_Security_Issues.html (thanks go to apathy for pointing it out!) the daemeon name when running (the service name) can be configured to be different to the process name!! Debian configuration sets the service name to be %hostname%-dir (which makes sense) so your hosts.allow has to have %hostname%-dir, NOT bacula-dir! HTH someone else. Greg ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
