This bug was fixed in the package bacula - 2.4.3-1ubuntu1
---
bacula (2.4.3-1ubuntu1) jaunty; urgency=low
* Store sd|fd|director passwords in debconf (LP: #222558)
- added debian/bacula-common.templates
- modified debian/bacula-common.postinst:
+ generate random
This bug was fixed in the package bacula - 2.4.3-1ubuntu1
---
bacula (2.4.3-1ubuntu1) jaunty; urgency=low
* Store sd|fd|director passwords in debconf (LP: #222558)
- added debian/bacula-common.templates
- modified debian/bacula-common.postinst:
+ generate random
I'll mark this bug as 'medium' at the moment. But this should be
resolved as soon as possible.
Kern, of course, any code would be welcome. It's clear that we should
generate password on postinstall of package, not during compile-time.
** Changed in: bacula (Ubuntu)
Importance: Undecided =
On Wednesday 24 September 2008 11:13:20 Ante Karamatić wrote:
I'll mark this bug as 'medium' at the moment. But this should be
resolved as soon as possible.
Kern, of course, any code would be welcome. It's clear that we should
generate password on postinstall of package, not during
I'll mark this bug as 'medium' at the moment. But this should be
resolved as soon as possible.
Kern, of course, any code would be welcome. It's clear that we should
generate password on postinstall of package, not during compile-time.
** Changed in: bacula (Ubuntu)
Importance: Undecided =
On Wednesday 24 September 2008 11:13:20 Ante Karamatić wrote:
I'll mark this bug as 'medium' at the moment. But this should be
resolved as soon as possible.
Kern, of course, any code would be welcome. It's clear that we should
generate password on postinstall of package, not during
I was not aware of this bug (sorry, I should look at them all), but I
think I can shed some light on it and even provide the code necessary
to fix it.
Basically the user is saying that each Bacula daemon generated needs a
shared secrete random password used for authentication, and these
passwords
I was not aware of this bug (sorry, I should look at them all), but I
think I can shed some light on it and even provide the code necessary
to fix it.
Basically the user is saying that each Bacula daemon generated needs a
shared secrete random password used for authentication, and these
passwords
I'm sorry I did not respond to this bug earlier. I missed Chuck's reply
in April. Kern is absolutely right, this is a packaging problem
inherited from Debian.
I didn't want to make the problem bigger than it acutally is. People who
are using Bacula should be aware of the fact that the software
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Which version is this?
Thanks
chuck
** Changed in: bacula (Ubuntu)
Status: New = Incomplete
--
password in bacula-fd.conf is not auto-generated
https://bugs.launchpad.net/bugs/222558
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
12 matches
Mail list logo
