Warning: This document is for the development version of Bareos Documentation. The main version is bareos-24.

Transport Encryption

Bareos uses TLS (Transport Layer Security) to provide secure network transport. For data encryption in contrast, please see the Data Encryption chapter. The initial Bacula encryption implementation has been written by Landon Fuller.

With Version >= 18.2.4 the TLS code has been enhanced by the TLS-PSK (Pre Shared Keys) feature which allows the daemons to setup an encrypted connection directly without using certificates. The library used for TLS is openSSL.

TLS Configuration Directives

Additional configuration directives have been added to all the daemons (Director, File daemon, and Storage daemon) as well as the various different Console programs. These directives are defined as follows:

TLS Enable (Dir->Director)

Enable TLS support. This is by default enabled. If no certificates are configured PSK (Pre Shared Keys) ciphers will be used. If the other side does not support TLS, or cleartext is configured the connection will be aborted. However, for downward compatibility with clients before Bareos-18.2 the daemons can omit transport encryption and cleartext will be sent.

TLS Require (Dir->Director)

Require TLS connection, for downward compatibility. This is by default disabled. However, if TlsRequire=yes, clients with a version before Bareos-18.2 will be denied if configured to use cleartext.

TLS Certificate (Dir->Director)

The full path and filename of a PEM encoded TLS certificate. It can be used as either a client or server certificate. It is used because PEM files are base64 encoded and hence ASCII text based rather than binary. They may also contain encrypted information.

TLS Key (Dir->Director)

The full path and filename of a PEM encoded TLS private key. It must correspond to the certificate specified in the TLS Certificate configuration directive.

TLS Verify Peer (Dir->Director)

Request and verify the peers certificate.

In server context, unless the TLS Allowed CN configuration directive is specified, any client certificate signed by a known-CA will be accepted.

In client context, the server certificate CommonName attribute is checked against the Address and TLS Allowed CN configuration directives.

TLS Allowed CN (Dir->Director)

Common name attribute of allowed peer certificates. If TLS Verify Peer=yes, all connection request certificates will be checked against this list.

This directive may be specified more than once as all parameters will we concatenated.

TLS CA Certificate File (Dir->Director)

The full path and filename specifying a PEM encoded TLS CA certificate(s). Multiple certificates are permitted in the file.

In a client context, one of TLS CA Certificate File or TLS CA Certificate Dir is required.

In a server context, it is only required if TLS Verify Peer is used.

TLS CA Certificate Dir (Dir->Director)

Full path to TLS CA certificate directory. In the current implementation, certificates must be stored PEM encoded with OpenSSL-compatible hashes, which is the subject name’s hash and an extension of .0.

In a client context, one of TLS CA Certificate File or TLS CA Certificate Dir is required.

In a server context, it is only required if TLS Verify Peer is used.

TLS DH File (Dir->Director)

Path to PEM encoded Diffie-Hellman parameter file. If this directive is specified, DH key exchange will be used for the ephemeral keying, allowing for forward secrecy of communications. DH key exchange adds an additional level of security because the key used for encryption/decryption by the server and the client is computed on each end and thus is never passed over the network if Diffie-Hellman key exchange is used. Even if DH key exchange is not used, the encryption/decryption key is always passed encrypted. This directive is only valid within a server context.

To generate the parameter file, you may use openssl:

create DH key

openssl dhparam -out dh1024.pem -5 1024

Getting TLS Certificates

To get a trusted certificate (CA or Certificate Authority signed certificate), you will either need to purchase certificates signed by a commercial CA or become a CA yourself, and thus you can sign all your own certificates.

Bareos is known to work well with RSA certificates.

You can use programs like xca or TinyCA to easily manage your own CA with a Graphical User Interface.

Example TLS Configuration Files

Examples of the TLS portions of the configuration files are listed below.

Bareos Director

bareos-dir.d/director/bareos-dir.conf

Director {                            # define myself
    Name = bareos-dir
    ...
    TLS Enable = yes     #yes by default
    TLS CA Certificate File = /etc/bareos/tls/ca.pem
    # This is a server certificate, used for incoming
    # (console) connections.
    TLS Certificate = /etc/bareos/tls/bareos-dir.example.com-cert.pem
    TLS Key = /etc/bareos/tls/bareos-dir.example.com-key.pem
    TLS Verify Peer = yes
    TLS Allowed CN = "bareos@backup1.example.com"
    TLS Allowed CN = "administrator@example.com"
}

bareos-dir.d/storage/File.conf

Storage {
    Name = File
    Address = bareos-sd1.example.com
    ...
    TLS Enable = yes     #yes by default
    TLS CA Certificate File = /etc/bareos/tls/ca.pem
    # This is a client certificate, used by the director to
    # connect to the storage daemon
    TLS Certificate = /etc/bareos/tls/bareos-dir.example.com-cert.pem
    TLS Key = /etc/bareos/tls/bareos-dir.example.com-key.pem
    TLS Allowed CN = bareos-sd1.example.com
}

bareos-dir.d/client/client1-fd.conf

Client {
    Name = client1-fd
    Address = client1.example.com
    ...
    TLS Enable = yes     #yes by default
    TLS CA Certificate File = /etc/bareos/tls/ca.pem
    TLS Certificate = "/etc/bareos/tls/bareos-dir.example.com-cert.pem"
    TLS Key = "/etc/bareos/tls/bareos-dir.example.com-key.pem"
    TLS Allowed CN = client1.example.com
}

Bareos Storage Daemon

bareos-sd.d/storage/bareos-sd1.conf

Storage {
    Name = bareos-sd1
    ...
    # These TLS configuration options are used for incoming
    # file daemon connections. Director TLS settings are handled
    # in Director resources.
    TLS Enable = yes     #yes by default
    TLS CA Certificate File = /etc/bareos/tls/ca.pem
    # This is a server certificate. It is used by connecting
    # file daemons to verify the authenticity of this storage daemon
    TLS Certificate = /etc/bareos/tls/bareos-sd1.example.com-cert.pem
    TLS Key = /etc/bareos/tls/bareos-sd1.example.com-key.pem
    # Peer verification must be disabled,
    # or all file daemon CNs must be listed in "TLS Allowed CN".
    # Peer validity is verified by the storage connection cookie
    # provided to the File Daemon by the Director.
    TLS Verify Peer = no
}

bareos-sd.d/director/bareos-dir.conf

Director {
    Name = bareos-dir
    ...
    TLS Enable = yes     #yes by default
    TLS CA Certificate File = /etc/bareos/tls/ca.pem
    # This is a server certificate. It is used by the connecting
    # director to verify the authenticity of this storage daemon
    TLS Certificate = /etc/bareos/tls/bareos-sd1.example.com-cert.pem
    TLS Key = /etc/bareos/tls/bareos-sd1.example.com-key.pem
    # Require the connecting director to provide a certificate
    # with the matching CN.
    TLS Verify Peer = yes
    TLS Allowed CN = "bareos-dir.example.com"
}

Bareos File Daemon

bareos-fd.d/client/myself.conf

Client {
    Name = client1-fd
    ...
    # you need these TLS entries so the SD and FD can
    # communicate
    TLS Enable = yes     #yes by default

    TLS CA Certificate File = /etc/bareos/tls/ca.pem
    TLS Certificate = /etc/bareos/tls/client1.example.com-cert.pem
    TLS Key = /etc/bareos/tls/client1.example.com-key.pem

    TLS Allowed CN = bareos-sd1.example.com
}

bareos-fd.d/director/bareos-dir.conf

Director {
    Name = bareos-dir
    ...
    TLS Enable = yes     #yes by default
    TLS CA Certificate File = /etc/bareos/tls/ca.pem
    # This is a server certificate. It is used by connecting
    # directors to verify the authenticity of this file daemon
    TLS Certificate = /etc/bareos/tls/client11.example.com-cert.pem
    TLS Key = /etc/bareos/tls/client1.example.com-key.pem
    TLS Verify Peer = yes
    # Allow only the Director to connect
    TLS Allowed CN = "bareos-dir.example.com"
}

Compatibility with Bareos File Daemon

Bareos File Daemon connection handshake probing

As from Bareos 18.2 all components by default establish a secure connection with encryption first, followed by the proprietary Bareos protocol. This is accomplished using TLS-PSK. Older components of Bareos than version 18.2 start a connection with a cleartext handshake without encryption.

For downward compatibility Bareos Director Daemons and Bareos Storage Daemons are able to connect to Bareos File Daemons older than version 18.2. In this case Director and Storage switch to the old protocol.

There are two connection modes of a File Daemon, active and passive. In contrast to a connection from an active Bareos File Daemon, the protocol version of a passive File Daemon has to be probed by the Director Daemon initially when a job is initiated. This information is stored in the configuration and immediately submitted to the Storage Daemon when the job is started.

The following sequence is used to figure out the right protocol version and to submit this information to the attached Bareos Storage Daemon:

Sequence diagram of a Bareos File Daemon connection

Bareos File Daemon 18.2 with Bareos before 18.2

Bareos File Daemon >= 18.2 can be used on a Bareos system before Bareos-18.2.

The older Bareos Director and Bareos Storage Daemon connect to Bareos File Daemon using the cleartext Bareos handshake before they can switch to TLS. If you want transport encryption then only TLS with certificates can be used. TLS-PSK is not possible with Bareos Director and Bareos Storage Daemon before Bareos-18.2.

However, it is also possible to disable transport encryption and use cleartext transport using the following configuration changes:

Bareos Director configuration

/etc/bareos/bareos-dir.d/client/bareos-fd.conf

Client {
  ...
  TlsEnable = no
  TlsRequire = no
  ...
}

/etc/bareos/bareos-dir.d/storage/bareos-sd.conf

Storage {
  ...
  TlsEnable = no
  TlsRequire = no
  ...
}

Bareos Storage Daemon configuration

/etc/bareos/bareos-sd.d/storage/bareos-sd.conf

Storage {
  ...
  TlsEnable = no
  TlsRequire = no
  ...
}

Bareos File Daemon configuration before 18.2

/etc/bareos/bareos-fd.d/client/bareos-fd.conf

Client {
  ...
  TlsEnable = no
  TlsRequire = no
  ...
}

/etc/bareos/bareos-fd.d/director/bareos-dir.conf

Director {
  ...
  TlsEnable = no
  TlsRequire = no
  ...
}

Bareos File Daemon before 18.2 with Bareos 18.2

Bareos File Daemon before 18.2 can be used on a Bareos system 18.2 onwards.

The newer Bareos Director and Bareos Storage Daemon connect to Bareos File Daemon using the cleartext Bareos handshake before they switch to TLS. If you want transport encryption only TLS with certificates can be used, not PSK as it is possible with Bareos 18.2.

However, it is also possible to disable transport encryption and use cleartext transport using the following configuration changes:

Bareos File Daemon configuration

/etc/bareos/bareos-fd.d/client/bareos-fd.conf

Client {
  ...
  TlsEnable = no
  TlsRequire = no
  ...
}

/etc/bareos/bareos-fd.d/director/bareos-dir.conf

Director {
  ...
  TlsEnable = no
  TlsRequire = no
  ...
}

Bareos Webui

Transport encryption between Bareos Webui and a Bareos Director can be configured on a per restricted named console basis.

TLS-PSK is not available between the Bareos WebUI and the Bareos Director, in the following you will set up TLS with certificates.

Please check the following configuration examples. A complete table of the directives in the directors.ini file see: Overview of the settings in the Bareos Webui directors.ini file

Note

For Bareos Webui the certificate file given by configuration parameter cert_file in directors.ini has to contain the certificate and the key in PEM encoding.

Configuration example for Bareos 17.2

/etc/bareos-webui/directors.ini

;------------------------------------------------------------------------------
; Section backup.example.com
;------------------------------------------------------------------------------
[backup.example.com]
enabled = "yes"
diraddress = "backup.example.com"
dirport = 9101
;catalog = "MyCatalog"
tls_verify_peer = false
server_can_do_tls = true
server_requires_tls = false
client_can_do_tls = true
client_requires_tls = true
ca_file = "/etc/bareos-webui/tls/ca.crt"
cert_file = "/etc/bareos-webui/tls/client.pem"
;cert_file_passphrase = ""
;allowed_cns = ""

/etc/bareos/bareos-dir.d/console/admin.conf

#
# Restricted console used by bareos-webui
#
Console {
  Name = admin
  Password = "123456"
  Profile = "webui-admin"
  TLS Enable = yes
  TLS Require = no
  TLS Verify Peer = no
  TLS CA Certificate File = /etc/bareos/tls/ca.crt
  TLS Certificate = /etc/bareos/tls/server.crt
  TLS Key = /etc/bareos/tls/server.pem
}

Configuration example for Bareos 18.2

Changed in version 18.2.

Warning

In Bareos version 18.2, the global certificates configured in the director resource in the director configuration need to be used. Before, the certificates configured in the console resource of the director configuration were used.

/etc/bareos-webui/directors.ini

;------------------------------------------------------------------------------
; Section backup.example.com
;------------------------------------------------------------------------------
[backup.example.com]
enabled = "yes"
diraddress = "backup.example.com"
dirport = 9101
;catalog = "MyCatalog"
tls_verify_peer = false
server_can_do_tls = true
server_requires_tls = false
client_can_do_tls = true
client_requires_tls = true
ca_file = "/etc/bareos-webui/tls/ca.crt"
cert_file = "/etc/bareos-webui/tls/client.pem"
;cert_file_passphrase = ""
;allowed_cns = ""

/etc/bareos/bareos-dir.d/director/bareos-dir.conf

Director {
   Name = bareos-dir
   QueryFile = "/usr/lib/bareos/scripts/query.sql"
   Maximum Concurrent Jobs = 10
   Password = "654321"
   Messages = Daemon
   Auditing = yes

   # Enable the Heartbeat if you experience connection losses
   # (eg. because of your router or firewall configuration).
   # Additionally the Heartbeat can be enabled in bareos-sd and bareos-fd.
   #
   # Heartbeat Interval = 1 min

   # remove comment in next line to load dynamic backends from specified directory
   # Backend Directory = /usr/lib64/bareos/backends

   # remove comment from "Plugin Directory" to load plugins from specified directory.
   # if "Plugin Names" is defined, only the specified plugins will be loaded,
   # otherwise all director plugins (*-dir.so) from the "Plugin Directory".
   #
   # Plugin Directory = "/usr/lib64/bareos/plugins"
   # Plugin Names = ""

   TLS Enable = yes
   TLS Require = no
   TLS Verify Peer = no
   TLS CA Certificate File = /etc/bareos/tls/ca.crt
   TLS Certificate = /etc/bareos/tls/server.crt
   TLS Key = /etc/bareos/tls/server.pem
}

Overview of the settings in the Bareos Webui directors.ini file

TLS settings for Bareos Webui

Directive	Type	Default value	Remark	Description
tls_verify_peer	boolean	false	Optional	TLS verif peer
server_can_do_tls	boolean	false	Required	Server (Bareos Director) can do TLS
server_requires_tls	boolean	false	Required	Server (Bareos Director) requires TLS
client_can_do_tls	boolean	false	Required	Client can do TLS
client_requires_tls	boolean	false	Required	Client requires TLS
ca_file	string		Required	Certificate authority file
cert_file	string		Required	Path to the certificate file which needs to contain the client certificate and the key in PEM encoding
cert_file_passphrase	string		Optional	Passphrase to unlock the certificate file given by cert_file
allowed_cns	string		Optional	Allowed common names

TLS Configuration Reference

To be able to communicate via TLS, TLS needs to be configured on both sides. In Bareos certain directives are used to set up TLS.

The following table explains the location of the relevant TLS configuration directives for all possible Bareos TCP connections. Each resource is referred to as <component>-<resource> to identify the exact configuration location. Refer to chapter Customizing the Configuration for more details about configuration.

In Bareos Version 18.2 the relevant resources for some connections had to be changed. Affected directives are marked with the applicable version and the respective resource is written in bold letters.

Remark: TLS-PSK is not available on Bareos components before Version 18.2.

TLS Configuration Reference

Config Directive / Connection No. [1]	TCP-Client		TCP-Server
1	Default Console	→	Director
Name [2]	*UserAgent* [4]		*UserAgent* [4]
Password [3]	Console-Director		Director-Director
Certificate directives	Console-Director		Director-Director
Tls Enable / Tls Require	Console-Director		Director-Director
2	Named Console	→	Director
Name [2]	Console-Console		Director-Console
Password [3]	Console-Console		Director-Console
Certificate directives [5], Version 17.2:	Console-Console		Director-Console
Certificate directives [5], Version 18.2:	Console-Console		Director-Director
Tls Enable / Tls Require	Console-Console		Director-Console
3	Director	→	File Daemon
Name, Version 17.2:	Director-Client		Client-Director
Name [2], Version 18.2:	Director-Director		Client-Director
Password [3]	Director-Client		Client-Director
Certificate directives [5], Version 17.2:	Director-Client		Client-Director
Certificate directives [5], Version 18.2:	Director-Client		Client-Client
Tls Enable / Tls Require	Director-Client		Client-Director
4	File Daemon	→	Director
Name, Version 17.2:	Client-Director		Director-Client
Name [2], Version 18.2:	Client-Client		Director-Client
Password [3]	Client-Director		Director-Client
Certificate directives [5], Version 17.2:	Client-Director		Director-Client
Certificate directives [5], Version 18.2:	Client-Director		Director-Director
Tls Enable / Tls Require	Client-Director		Director-Client
5a, 5b	Director	→	Storage Daemon
Name, Version 17.2:	Director-Storage		Storage-Director
Name [2], Version 18.2:	Director-Director		Storage-Director
Password [3]	Director-Storage		Storage-Director
Certificate directives [5], Version 17.2:	Director-Storage		Storage-Director
Certificate directives [5], Version 18.2:	Director-Storage		Storage-Storage
Tls Enable / Tls Require	Director-Storage		Storage-Director
6	File Daemon	→	Storage Daemon
Name, Version 17.2:	not defined		not defined
Name [2], Version 18.2:	job name		job name
Password [3]	job session key		job session key
Certificate directives [5], Version 17.2:	Director-Storage		Storage-Director
Certificate directives [5], Version 18.2:	Director-Storage		Storage-Storage
Tls Enable / Tls Require	Director-Storage		Storage-Director
7	Storage Daemon	→	File Daemon
Name, Version 17.2:	not defined		not defined
Name [2], Version 18.2:	job name		job name
Password [3]	job session key		job session key
Certificate directives [5], Version 17.2:
Certificate directives [5], Version 18.2:	Storage-Storage		Client-Client
Tls Enable / Tls Require	Director-Client		Client-Client
8	Storage Daemon	→	Storage Daemon
Name, Version 17.2:	not defined		not defined
Name [2], Version 18.2:	job name		job name
Password [3]	job session key		job session key
Certificate directives [5]	Storage-Storage		Storage-Storage
Tls Enable / Tls Require	Director-W Storage		Director-W Storage
9	Traymon	→	Director
Name [2]	Traymon-Traymon		Director-Console
Password [3]	Traymon-Traymon		Director-Console
Certificate directives [5]	Traymon-Director		Director-Director
Tls Enable / Tls Require	Traymon-Director		Director-Console
10	Traymon	→	FD
Name [2]	Traymon-Traymon		Client-Director
Password [3]	Traymon-Client		Client-Director
Certificate directives [5]	Traymon-Client		Client-Client
Tls Enable / Tls Require	Traymon-Client		Client-Director
11	Traymon	→	SD
Name [2]	Traymon-Traymon		Storage-Director
Password [3]	Traymon-Storage		Storage-Director
Certificate directives [5]	Traymon-Storage		Storage-Storage
Tls Enable / Tls Require	Traymon-Storage		Storage-Director

Footnotes

[1]

The connection number references this table: Legend for full connection overview

[2] (1,2,3,4,5,6,7,8,9,10,11)

From Version 18.2 onwards this is identical to the TLS-PSK Identitiy

[3] (1,2,3,4,5,6,7,8,9,10,11)

From Version 18.2 onwards this is identical to the TLS-PSK Pre-Shared Key

[4] (1,2)

The name of the default console is predefined and cannot be changed

[5] (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16)

Certificate directives are: TlsVerifyPeer, TlsCaCertificateFile, TlsCaCertificateDir, TlsCertificateRevocationList, TlsCertificate, TlsKey, TlsAllowedCn