Control: found 26+20191223-1 On Feb 23, Bastian Germann <bastiangerm...@fishpost.de> wrote:
> All of the GPL-2+ licensed executables contained in the kmod binary > package link to libcrypto even though they do not have any OpenSSL > license exception. ftp-master considers this a serious issue. So please > remove this optional dependency or ask upstream for a license exception. The large number of contributors to kmod obviously makes impossible getting a license exception, also considering that only Debian cares about linking GPL'ed software with OpenSSL. Since only libkmod (which is LGPL'ed), and not the actual commands, is linked with OpenSSL, and the libkmod symbols do not change depending if OpenSSL support is enabled or not, and the patches which introduced OpenSSL support did not touch the commands, then I think that the commands are obviously not a derivative work of OpenSSL. You can also easily verify that the commands are not linked with OpenSSL by looking at the build logs of the package. Also, the next major release of OpenSSL will be relicensed with the ASLv2 anyway, which is compatible with the GPLv3. For these reasons I have no interest and no plans to do anything about this, and I am quite annoyed that I had to spend my time researching these details and then explaining them to you. -- ciao, Marco
signature.asc
Description: PGP signature
