bacula client configuration is broken out of the box
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bacula (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: bacula-client
Hello,
I am a member of the bacula dev team, my role is rpm packaging. I recently installed Kubuntu-8.04 on my daughter's machine (I have bacula running on my local Kubuntu-8.04 server). When installing the bacula client package I spent some minimal time this past weekend figuring out why your package does not work "out of the box" as it were. The client was available on the localhost but not available on the network. To put it simply, someone has apparently decided that packaging should address security concerns, and thus your package configures the client to listen only on localhost. While this might be apparent to me or other developers on the bacula project, it is not, most likely, apparent to the majority of users and we do not want this to reflect on the bacula project as a whole. We, as an upstream dev team feel that these concerns should be relegated to firewalls, etc. and not to individual applications. Thus we consider your packages broken. Please include <email address hidden> in any replies. Thanks in advance for your consideration.
Regards,
Scott
Hi Scott,
Thanks for taking the time to get in touch with the Ubuntu Development team. We understand that bacula is planning to send a couple of developers to Fosscamp, and think that might be an appropriate forum to collaborate on a final solution. I'll attend Fooscamp and I'm ready to discuss this issue with them.
Is is this an acceptable solution for you?