Hi Romeo,

Thanks!  Just so I understand correctly...

The bacula-fd running on the clients communicate with the bacula server using the password in client's bacula-fd.conf.  This authentication on the "wire" is actually encrypted.  Is this correct?

-craig

On Tue, May 5, 2015 at 3:43 PM, Romeo Theriault <romeot AT hawaii DOT edu> wrote:

Hi Craig, 

See [1]:

You should restrict access to the Bacula configuration files, so that the passwords are not world-readable. The Bacula daemons are password protected using CRAM-MD5 (i.e. the password is not sent across the network). This will ensure that not everyone can access the daemons. It is a reasonably good protection, but can be cracked by experts.

[1] http://www.bacula.org/5.1.x-manuals/en/main/main/Bacula_Security_Issues.html

On Tue, May 5, 2015 at 8:35 PM, Craig Shiroma <shiroma.craig.2 AT gmail DOT com> wrote:

Hello,

I was wondering...

Are all of the passwords exchanges used by Bacula (both server and client daemons) encrypted when going over the "wire"?

Thanks in advance,

Craig Shiroma

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users