Re: Fwd: PostgreSQL: WolfSSL support - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Fwd: PostgreSQL: WolfSSL support
Date
Msg-id 71528.1593269806@sss.pgh.pa.us
Whole thread Raw
In response to Re: Fwd: PostgreSQL: WolfSSL support  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Fwd: PostgreSQL: WolfSSL support  (Bruce Momjian <bruce@momjian.us>)
Re: Fwd: PostgreSQL: WolfSSL support  (Christoph Berg <myon@debian.org>)
Re: Fwd: PostgreSQL: WolfSSL support  (Felix Lechner <felix.lechner@lease-up.com>)
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> On Sat, Jun 27, 2020 at 02:50:27PM +0200, 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.

> Uh, wolfSSL is GPL2:
>     https://www.wolfssl.com/license/

Readline is GPLv3+ (according to Red Hat's labeling of that package
anyway, didn't check the source).  So they'd be compatible, while
openssl's license is nominally incompatible with GPL.  As I recall,
Debian jumps through some silly hoops to pretend that they're not
using openssl and readline at the same time with Postgres, so I
can definitely understand Christoph's interest in an alternative.

However, judging from the caveats mentioned in the initial message,
my inclination would be to wait awhile for wolfSSL to mature.

In any case, the patch as written seems to *remove* the option
to compile PG with OpenSSL.  The chance of it being accepted that
way is indistinguishable from zero.  We've made some efforts towards
separating out the openssl-specific bits, so the shape I'd expect
from a patch like this is to add some parallel wolfssl-specific bits.
There probably are more such bits to separate, but this isn't the
way to proceed.

            regards, tom lane



pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: [PATCH] Remove Extra palloc Of raw_buf For Binary Format In COPY FROM
Next
From: Bruce Momjian
Date:
Subject: Re: Fwd: PostgreSQL: WolfSSL support