Re: GPL exception for the OpenSSL library
My question is: do you think this license exception is
acceptable for use? That is, does it prevent the proprietary hijacking
of the linked GPL-incompatible library? Can you see any flaws in this?
I see one possible flaw: if someone includes a different COPYING.OpenSSL
file, this notice would give permission for linking with something
under that replaced file. I think that's a bug. It needs to state
the OpenSSL license in some more reliable way.
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org