📜 ⬆️ ⬇️

How to get rid of the GPL?

There is such a good library: MatrixSSL . Small, smart, safe ... and, most importantly, with a completely sane API, and not the nightmare in OpenSSL. But it has one drawback: the authors released the library under the GPL, and not the LGPL, in order to encourage users to buy the paid version.

In this regard, I have a question for those who understand licensing: is it possible to avoid licensing an application using MatrixSSL under the GPL if you use the following trick. A separate application is written under the GPL that works as a network service: accepts RPC requests, answers them ... and which actually provides access to the MatrixSSL API through this RPC interface. And the main application, even though it will use this network service, will no longer be under the GPL.

Logically, this should be legal. After all, commercial applications constantly use network services provided by GPL-applications.
')
Update: Judging by the comments, it is necessary to clarify once again (and, probably, many, many times) - I have nothing against paying the authors of such a cool library. But I don’t want to release my software under the GPL because of it , I prefer the Public Domain or, in extreme cases, other open licenses, but not the GPL-virus!

Source: https://habr.com/ru/post/44741/


All Articles