Re: check_ssl_key_file_permissions should be in be-secure-common.c

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: check_ssl_key_file_permissions should be in be-secure-common.c
Date: 2018-04-02 15:39:57
Message-ID: 7eab949e-a406-2a93-4bee-bacdf149b0ee@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4/2/18 02:51, Michael Paquier wrote:
> It seems to me that this routine should be logically put into
> be-secure-common.c so as future SSL implementations can use it. This
> makes the code more consistent with the frontend refactoring that has
> happened in f75a959. I would not have bothered about this refactoring
> if be-secure-openssl.c did not exist yet, but as it does I think that we
> should bite the bullet, and do that for v11 so as a good base is in
> place for the future.

committed

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-04-02 15:49:56 Re: disable SSL compression?
Previous Message Robert Haas 2018-04-02 15:26:38 Re: [HACKERS] Restrict concurrent update/delete with UPDATE of partition key