Re: Support for NSS as a libpq TLS backend - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Support for NSS as a libpq TLS backend
Date
Msg-id D187206C-B942-484B-AB39-5AD25191D6AB@yesql.se
Whole thread Raw
In response to Re: Support for NSS as a libpq TLS backend  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Support for NSS as a libpq TLS backend  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
> On 3 Jun 2021, at 19:37, Jeff Davis <pgsql@j-davis.com> wrote:
>
> On Tue, 2020-10-27 at 23:39 -0700, Andres Freund wrote:
>> Maybe we should just have --with-ssl={openssl,nss}? That'd avoid
>> needing
>> to check for errors.
>
> [ apologies for the late reply ]
>
> Would it be more proper to call it --with-tls={openssl,nss} ?

Well, we use SSL for everything else (GUCs, connection params and env vars etc)
so I think --with-ssl is sensible.

However, SSL and TLS are used quite interchangeably these days so I think it
makes sense to provide --with-tls as an alias.

--
Daniel Gustafsson        https://vmware.com/




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: SSL SNI
Next
From: Tom Lane
Date:
Subject: Re: SSL SNI