[dm-crypt] License Clarification
npmccallum at redhat.com
Thu Nov 10 20:41:24 CET 2016
In reviewing the license choices of a set of my projects, I have
noticed an inconsistency in licensing and I would like to receive some
There is a commit that changes some of the code to LGPLv2.1+:
However, the main header still reads GPLv2+:
Further, the API examples have LGPLv2.1+:
Again, the openssl crypto backend are licensed as LGPLv2.1+ w/ openssl
exception. However, this exception doesn't seem to apply to the whole
In short, it is very unclear to me how this licensing is supposed to work.
The best I can ascertain is this:
crypto-backend (LGPLv2+) ==> libcryptsetup (GPLv2+) ==> API examples (LGPLv2+)
It would, thus, seem to me that the API examples are incompatibly
licensed and cannot actually link against libcryptsetup.
Further, it seems to me that the crypto-backend can link against
openssl, but not libcryptsetup itself. This further implies that
consumers of libcryptsetup cannot link against openssl.
Have I understood this correctly?
More information about the dm-crypt