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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Sep 12 04:25:29 PDT 2022


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

Philippe Normand <philn at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |philn at igalia.com

--- Comment #12 from Philippe Normand <philn at igalia.com> ---
(In reply to Michael Catanzaro from comment #7)
[...]
> Anyway, at first I was concerned about this because we need Zan's libgcrypt
> backend for WebCrypto, but then I discovered that Sony has already developed
> an alternative OpenSSL backend for WebCrypto that we could use instead. I
> was planning to propose switching WebKitGTK 2.32 to use the OpenSSL backend
> by default if OpenSSL 3 is detected, while falling back to libgcrypt for
> older versions of OpenSSL.
> 
> (We're planning to ship OpenSSL 3 in Fedora 34. This OpenSSL license change
> is a really big deal. Previously, we could not safely link WebKit directly
> to OpenSSL, but now with this license change, I wouldn't be surprised if
> OpenSSL begins slowly replacing other crypto libraries over the next decade.)

FWIW, the FDO SDK now ships OpenSSL 3, since the 22.08 release. I dunno what is the status in distros, but would this proposal of depending on OpenSSL 3 now be actually doable?

-- 
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/20220912/43173268/attachment.htm>


More information about the webkit-unassigned mailing list