On 05/11/2016 08:11 PM, Heitor Faria wrote:
>
>> On 2016-05-10 23:42, Kern Sibbald wrote:
>>> Checking for @PASSWORD@ and failing to run is quite reasonable.
>>> However, during the installation process (before running) the @PASSWORD@
>>> as well as a lot of other variables should be replaced. In the case of
>>> @PASSWORD@ it should be replaced by a random string by openssl.
>>
>> That's great, but if I'm installing a server from rpms today, and a
>> client on another machine from another rpm tomorrow, how am I going to
>> end up with the exact same random openssl string on both?
>
> Hello, Dimitri: sorry if I get this wrong, but when attaching a new
client to Bacula Director (add a new Client Resource) aren't you
supposed to copy the auto-generated password from the client side
installation (Ctrl+c, Ctrl+v)?
Is this new in 7.latest? -- every client gets their own password?
I'm still on 7.2 and that has 2 director passwords: regular and tray
monitor. Yes, they do need to be copied to the clients and @@PASSWORD@@
strings serve to indicate that the admin failed to do so. The point is
they're generated once when installing the director; for every other
installation: fd, sd, console, they should be, as you say, copy-pasted
-- not "replaced by a random string by openssl".
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
