[Bug 286643] Re: bacula client configuration is broken out of the box

Kern Sibbald kern at sibbald.com
Tue Oct 21 20:47:18 BST 2008

On Tuesday 21 October 2008 20:20:04 Ante Karamatić wrote:
> I would just like to present my opinion on this one...
> This change was introduced in Debian as fix for Debian bug 367105:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367105
> Both configurations have valid use cases. I'm kind of in favor of
> having bacula file daemon listening only on localhost, as it is now.
> Why? Here is why...
> Bacula will never work out of box, cause of lots of configuration
> options that should be changed after installation. Changing listening
> IP address is just a tip of an iceberg.

The standard Bacula rpms do work out of the box, as does the SQLite make 
install.   Since .debs are better (I am not at all being sarcastic here), why 
cannot they do the same thing, or at least attempt to approach it?

> On the other hand, people that don't have any clue about bacula, and
> are just testing the software, are in danger. I would advise not
> changing default at least until we solve bug #222558 - each bacula
> client and daemon have the same password. This is cause password is
> generated on compile time.
> IMHO, talking about this and working on this issue should be
> post-intrepid.

A couple of points here:

Following your logic on the localhost problem, we arrive at the following:
If you want to make daemons secure and hobble them to localhost then please do 
it uniformly to DNS, Apache, SSH, and the other daemons that can be used 
internally without connection to the Internet, because I may not have a clue 
about how they work and just want to test them. (A bit simplistic, but you 
probably get the idea).

Concerning the random password problem: The rpms created by Bacula have had 
random passwords installed for many years now. It is really quite easy to 
fix. I mentioned this problem in the .debs and the solution to the Debian 
maintainer quite a long time ago (probably years).  I have also sent the .deb 
scripts that we  (Bacula) use internally to the Ubuntu Bacula packaging crew.  
Our .deb packages when installed produce random passwords.

I'll leave it to you if/when to change anything.

Bacula Project Manager

bacula client configuration is broken out of the box
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in ubuntu.

More information about the Ubuntu-server-bugs mailing list