[Webkit-unassigned] [Bug 214813] New: [WPE][GTK] Add WebKitWebExtension API to indicate web extension does not link to GPL code, and use it to gate WebRTC access (?)
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sun Jul 26 14:04:57 PDT 2020
https://bugs.webkit.org/show_bug.cgi?id=214813
Bug ID: 214813
Summary: [WPE][GTK] Add WebKitWebExtension API to indicate web
extension does not link to GPL code, and use it to
gate WebRTC access (?)
Product: WebKit
Version: WebKit Nightly Build
Hardware: PC
OS: Linux
Status: NEW
Severity: Normal
Priority: P2
Component: WebRTC
Assignee: webkit-unassigned at lists.webkit.org
Reporter: mcatanzaro at gnome.org
CC: bugs-noreply at webkitgtk.org, youennf at gmail.com
Problem statement: libwebrtc uses BoringSSL, which uses the OpenSSL license, which is not GPL-compatible and cannot be linked to GPL code. Several applications use GPL-licensed web extensions -- I can think of three off the top of my head -- so we exclude Source/ThirdParty/libwebrtc in Tools/[gtk,wpe]/manifest.txt.in to ensure libwebrtc is never distributed in releases and cannot be linked with GPL code.
Strawman proposal: void webkit_web_extension_allow_gpl_incompatible_features(gboolean);
If no web extensions are loaded, or if every loaded web extension calls this function, then we can enable WebRTC. If any WebKitWebExtension fails to call the function, we get no WebRTC. We would then relicense the Epiphany web extension to LGPLv2+ and enjoy WebRTC to heart's content.
Downside of this plan: we'd have to change WebKit to dlopen libwebrtc if and only if using GPL-incompatible code is allowed. Not sure how hard that would be.
--
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/20200726/4ab0bb9d/attachment-0001.htm>
More information about the webkit-unassigned
mailing list