Am Samstag 20 März 2010 13:20:17 schrieb Ludovic Rousseau: > This trick is allowed by (L)GPL v2. It is called Tivoization [1]. > (L)GPL v3 was specifically designed to prevent that.
yes and no. GPL v2 had not much protection against closed and sealed devices, and GPL v3 improves on that. for LGPL people had already thought about "dummy" functions in LGPL libraries, that bridge LGPL code to some closed code, and the closed code would be unavailable. LGPL (at least v2.1 I think) has already some protection against that, and I guess LGPL 3 improves on that too. > But since OpenSC is "LGPL version 2.1 of the License, or (at your > option) any later version" any user can use LGPL v3 to enforce the > anti-Tivoization mechanism. so as copyright holder, if we put several licenses on some code (we do with the "or later" clause), then we allow everyone else to decide which license to accept and to follow. i.e. in a legal issue you would need to ask first, which license they have choosen, and then show they didn't respect it properly. worst case: show that they respected none of the applicable licenses. Regards, Andreas _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
