This problem exists because the build-process of the package compiles against GnuTLS insteaed of OpenSSL. The encryption features are only supported when compiling with OpenSSL.
In order to change from GnuTLS to OpenSSL, the following changes have to be applied to the source tree: diff -Naur bareos-14.2.6-gnutls/debian/control bareos-14.2.6-openssl/debian/control --- bareos-14.2.6-gnutls/debian/control 2016-04-02 00:12:43.000000000 +0200 +++ bareos-14.2.6-openssl/debian/control 2016-09-10 11:51:27.000000000 +0200 @@ -15,7 +15,7 @@ liblzo2-dev, libqt4-dev, libreadline-dev, - libgnutls28-dev, + libssl-dev, libwrap0-dev, libx11-dev, libsqlite3-dev, libmysqlclient-dev, libpq-dev, diff -Naur bareos-14.2.6-gnutls/debian/rules bareos-14.2.6-openssl/debian/rules --- bareos-14.2.6-gnutls/debian/rules 2016-04-02 00:12:43.000000000 +0200 +++ bareos-14.2.6-openssl/debian/rules 2016-09-10 11:48:47.000000000 +0200 @@ -54,8 +54,8 @@ --with-mysql \ --with-sqlite3 \ --with-tcp-wrappers \ - --without-openssl \ - --with-gnutls \ + --with-openssl \ + --without-gnutls \ --with-dir-user=$(DIRECTOR_DAEMON_USER) \ --with-dir-group=$(DAEMON_GROUP) \ --with-sd-user=$(STORAGE_DAEMON_USER) \ However, the package maintainer might have had good reasons to change from OpenSSL to GnuTLS. Funnily, even though the package is currently built with GnuTLS, the binary package still depends on OpenSSL, due to a dependency defined in the control file. I guess this was just forgotten when changing from OpenSSL to GnuTLS, but it means that when changing back to OpenSSL, this actually does not have an effect on the binary dependencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611348 Title: support for pki missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bareos/+bug/1611348/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
