On Thu, 2014-02-06 at 18:49 +0100, Nikos Mavrogiannopoulos wrote: > I think making openconnect gpl when compiled in windows isn't very > unreasonable, but you could also have the tun device to be provided > externally in that platform. The LGPL on openconnect was historically just for compatibility with OpenSSL, and a modicum of laziness on my part ? getting "LGPL" past the Intel legal review to release openconnect in the first place was easier than any custom "GPL with exception for OpenSSL" text would have been. However, it has led to some interesting usage, such as Shimo which uses libopenconnect under the LGPL. I'm fairly happy with that, and wouldn't want to rule out the possibility of someone doing something similar for Windows. I'm also not entirely sure I want to deal with the complexity/ambiguity of having files under multiple licences, and "if you use this bit of code, then it has to be GPL". I'd rather make an effort to have the Windows tun code under LGPL, I think. -- dwmw2 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5745 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20140206/6e372f63/attachment-0001.bin>
