-Bacula may be linked with any libraries permitted under the GPL,
-or with any non-GPLed libraries, including OpenSSL, that are
-required for its proper functioning, providing the source code of
-those non-GPLed libraries is non-proprietary and freely
-available to the public.
+As a special exception to the GPLv2, the Bacula Project gives
+permission to link the code of its release of Bacula with the OpenSSL
+project's "OpenSSL" library (or with modified versions of it that use
+the same license as the "OpenSSL" library), and distribute the linked
+executables. You must obey the GNU General Public License in all
+respects for all of the code used other than "OpenSSL".
+
+As a special exception to the GPLv2, the Bacula Project gives
+permission to link the code of its release of the Bacula Win32 File
+daemon with the Microsoft supplied Volume Shadow Copy (VSS) libraries
+and distribute the linked executables. You must obey the GNU General
+Public License in all respects for all of the code used other than for
+the Microsoft VSS code, where you must obey their license terms.
+
+The Bacula Project gives permission for plugins with GPLv2 compatible
+licenses to be loaded and distributed with the Bacula executables as
+long as the combined work is distributed under the terms listed in the
+Bacula LICENSE file. A full list of GPLv2 compatible licenses can be
+found at: http://www.fsf.org/licensing/licenses/. If you wish to load
+or distribute plugins with different licensing terms please contact
+the Bacula Project at: license@bacula.org
+
+===================================
+
+
+What follows is information from the authors of the code:
+
+License:
+To the best of our knowledge, all code used in Bacula that is
+copyrighted by a third party has licenses that are compatible
+with the OpenSSL license, and so with the exception that we have
+made to the GPLv2 above, Bacula can be freely linked and distributed
+with the OpenSSL libraries.