Re: ssl passphrase callback

Andrew Dunstan <andrew.dunstan@2ndquadrant.com>

From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: "asaba.takanori@fujitsu.com" <asaba.takanori@fujitsu.com>, 'Andreas Karlsson' <andreas@proxel.se>, Thomas Munro <thomas.munro@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>, Bruce Momjian <bruce@momjian.us>, Magnus Hagander <magnus@hagander.net>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, Simon Riggs <simon@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-03-21T13:18:26Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Provide a TLS init hook

On 3/19/20 4:10 AM, asaba.takanori@fujitsu.com wrote:



> Trailing space:
>
> 220 +           X509v3 Subject Key Identifier:
> 222 +           X509v3 Authority Key Identifier:


We're going to remove all the text, so this becomes moot.


>
> Missing "d"(password?):
>
> 121 +/* init hook for SSL, the default sets the passwor callback if appropriate */
>

Will fix, thanks.


cheers


andrew


-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services