Re: Support for NSS as a libpq TLS backend

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Support for NSS as a libpq TLS backend
Date: 2020-09-04 01:23:34
Message-ID: 20200904012334.GF19499@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 03, 2020 at 03:26:03PM -0400, Andrew Dunstan wrote:
>> The 0001 patch isn't strictly necessary but it seems reasonable to address the
>> various ways OpenSSL was spelled out in the docs while at updating the SSL
>> portions. It essentially ensures that markup around OpenSSL and SSL is used
>> consistently. I didn't address the linelengths being too long in this patch to
>> make review easier instead.
>
> I'll take a look.

Adding a <productname> markup around OpenSSL in the docs makes things
consistent. +1.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-09-04 01:25:22 Re: [NBTREE] Possible NULL pointer dereference (backend/access/nbtree/nbutils.c)
Previous Message Bruce Momjian 2020-09-04 01:21:49 Re: BUG #16419: wrong parsing BC year in to_date() function