[Webkit-unassigned] [Bug 216201] [GTK]: RFE: remove using libgcrypt

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=216201

--- Comment #10 from Michael Catanzaro <mcatanzaro at gnome.org> ---
I agree we need to avoid OpenSSL license, because only Red Hat allows combining OpenSSL license with GPLv2.

(In reply to Carlos Alberto Lopez Perez from comment #9)
> So my understanding is that if we switch WebKit to use OpenSSL then WebKit
> itself will be incompatible (license-wise) with GPLv2-only applications (or
> libraries).
> 
> I'm missing something here?

That's all correct. I think it doesn't matter, though. (a) I don't know of any real GPLv2-only application that uses WebKit. Actual apps are GPLv2-or-later, which is OK since it automatically upgrades to GPLv3-or-later. (b) Even if such an application does exist, I'm unsympathetic, since GPLv2-only license is strongly discouraged by GNU/FSF. Applications using it should know they are setting themselves up for pain and license trouble if they aren't very careful about what they link to.

So I think, in practice, we should be fine as long as we are careful to never link to older OpenSSL versions. (Sadly, it seems BoringSSL will stick with the OpenSSL license, so this only applies to upstream OpenSSL.)

One more thing: glib-networking *might* (or might not) eventually switch its default backend to OpenSSL (if OpenSSL v3 is available) as well.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20201118/3efba774/attachment.htm>