On Wednesday 08 December 2010 15:39:26 ext Dave Neary, you wrote: > Patrick Ohly wrote: > > Second, as mentioned in #7777 and elsewhere [4], there is a license > > conflict between OpenSSL and GPL. Does opening OpenSSL via dlopen() at > > runtime really work around this conflict? I'm not a lawyer, but given > > that the way how linking is achieved is typically not specified in > > detail in licenses, I doubt that using dlopen() instead of ld.so really > > works around the license issue. > > I am definitely not a lawyer, but I have previously worked for a company > who routinely included functionality at runtime if we detected the > presence of certain GPL incompatible shared objects. We did receive > legal advice that this was not incompatible with the GPL, since we (the > application authors) were not shipping the non-GPL & GPL code together.
Neither am I, but I doubt that way works if a MeeGo vendor ships both (L)GPL'd Qt and LGPLv2-incompatible OpenSSL on its device. There are other ways out though: - claim that OpenSSL is a component of the "operating system", hence needs not be (L)GPL'd. - use GnuTLS or NSS instead of OpenSSL, - use (L)GPL version 3, which I think is on-purpose compatible with OpenSSL- style licenses (obviously not an option for MeeGo, just for completeness). -- Rémi Denis-Courmont Nokia Devices R&D, Maemo Software, Helsinki _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
