Hi Bhaskar,
On Mon, 29 Sep 2014, Bhaskar, K.S wrote:
GT.M does not require OpenSSL, does not statically link to it, and does
not in a strict sense, depend on OpenSSL. But there is a looser
relationship / dependency.
hmm, while looking at the Debian package, I found the following comment:
"The upstream V6.2-000 CMakeLists.txt file built only one of three
possible encryption plugin libraries. This meant that the debian fis-gtm
package was missing a core piece of the distributed binaries. Upstream will
apply this change to the next release after internal review."
Further the Debian package contains:
libgtmcrypt_openssl_BLOWFISHCFB.so
libgtmcrypt_gcrypt_AES256CFB.so
libgtmcrypt_openssl_AES256CFB.so
So at least the version in the Debian package is actually linked with
OpenSSL.
As the OpenSSL license contains (advertising) restrictions[1] that are not
allowed by the AGPL, the AGPL must be extended by an exception clause.
Thorsten
[1]https://en.wikipedia.org/wiki/OpenSSL#Licensing
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive:
https://lists.debian.org/[email protected]
