| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org>, Felix Lechner <felix(dot)lechner(at)lease-up(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Fwd: PostgreSQL: WolfSSL support |
| Date: | 2020-06-28 08:18:12 |
| Message-ID: | b7c1c741-9e18-3751-387f-9dd2e72b0193@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-06-27 14:50, Christoph Berg wrote:
> Re: Peter Eisentraut
>> What would be the advantage of using wolfSSL over OpenSSL?
>
> Avoiding the OpenSSL-vs-GPL linkage problem with readline.
We have added support for allegedly-OpenSSL compatible libraries such as
LibreSSL before, so some tweaks for wolfSSL would seem acceptable.
However, I doubt we are going to backpatch them, so unless you want to
take responsibility for that as a packager, it's not really going to
help anyone soon. And OpenSSL 3.0.0 will have a new license, so for the
next PostgreSQL release, this problem might be gone.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-06-28 08:33:53 | Re: pgsql: Enable Unix-domain sockets support on Windows |
| Previous Message | Noah Misch | 2020-06-28 06:20:04 | Re: Raising stop and warn limits |