-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kern Sibbald wrote:
| I had to modify the Bacula GPL license to be acceptable to Debian (I'm
not in
| the least complaining as I respect their position). This was because
| OpenSSL, which for some reason is not OpenSource or at least was not
at the
| time considered to be OpenSource by Debian (I didn't look into the
details).
| Bacula never used OpenSSL at that time, but it "touched" it by the
fact that
| Bacula was linked with the MySQL libraries which might require that
OpenSSL
| be linked with Bacula. I modified my GPL license to make an exception
for
| OpenSSL and all such software that provides the source code.
It's worth noting that OpenSSL is released under a very liberal license
that is unfortunately considered to be "GPL incompatible" -- thus
limiting its use by GPL software.
The license is akin to the old 4-clause BSD license, and includes
several advertising clauses:
http://www.openssl.org/source/license.html
~ * 3. All advertising materials mentioning features or use of this
~ * software must display the following acknowledgment:
~ * "This product includes software developed by the OpenSSL Project
~ * for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
~ * 6. Redistributions of any form whatsoever must retain the following
~ * acknowledgment:
~ * "This product includes software developed by the OpenSSL Project
~ * for use in the OpenSSL Toolkit (http://www.openssl.org/)"
~ * 3. All advertising materials mentioning features or use of this
~ * software must display the following acknowledgement:
~ * "This product includes cryptographic software written by
~ * Eric Young ([EMAIL PROTECTED])"
~ * The word 'cryptographic' can be left out if the routines from the
~ * library being used are not cryptographic related :-).
~ * 4. If you include any Windows specific code (or a derivative
~ * thereof) from the apps directory (application code) you must
~ * include an acknowledgement:
~ * "This product includes software written by Tim Hudson
([EMAIL PROTECTED])"
This is in conflict with the following clause from the GPL:
6. Each time you redistribute the Program (or any work based on the
~ Program), the recipient automatically receives a license from the
~ original licensor to copy, distribute or modify the Program subject to
~ these terms and conditions. You may not impose any further
~ restrictions on the recipients' exercise of the rights granted herein.
I think Kern's point is well-illustrated -- it can be complicated and
troublesome to try and mix GPL and non-GPL code, even if the code
involved is all available under relatively liberal open source licenses.
This is a good reminder that we should add the appropriate
acknowledgments to the manual.
- -landonf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDD1EclplZCE/15mMRAh0HAKCKAlcYR7cDJHIBSQDQueyqW8rlNQCbBhsq
KqFFmIko0D/QE3xfEWj3xYY=
=duYs
-----END PGP SIGNATURE-----
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
