<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK][EFL] CryptoDigest implementation depends on GnuTLS with LGPLv3+/GPLv2+ deps"
href="https://bugs.webkit.org/show_bug.cgi?id=162913#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK][EFL] CryptoDigest implementation depends on GnuTLS with LGPLv3+/GPLv2+ deps"
href="https://bugs.webkit.org/show_bug.cgi?id=162913">bug 162913</a>
from <span class="vcard"><a class="email" href="mailto:olivier.blin@softathome.com" title="Olivier Blin <olivier.blin@softathome.com>"> <span class="fn">Olivier Blin</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=162913#c12">comment #12</a>)
<span class="quote">> Even if we replace the GnuTLS dependency for the crypto code, you will
> probably end using it anyway via libsoup -> glib-networking -> gnutls
> backend.</span >
Licensing concerns may be a bit different for glib-networking, since gnutls and its deps are not linked directly, but loaded as a dynamic plugin.
<span class="quote">> * We will try to avoid using GnuTLS because of the above. But keep in mind
> that even when we end doing that, you can end anyways using GnuTLS without
> realizing this via the glib-networking TLS backend dependency.</span >
Ok, I will propose a gcrypt backend, covering CryptoDigest and HMAC.
<span class="quote">> So in the end this (carefully selecting which libraries and versions go into
> the build) is something the distributor should care about, and not us.</span >
Right</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>