Re: TCP Wrappers - Mailing list pgsql-hackers

From Lou Picciano
Subject Re: TCP Wrappers
Date
Msg-id EFC35422-2227-4C0F-8DB1-6357ACBB2FB4@comcast.net
Whole thread Raw
In response to Re: TCP Wrappers  (Steve Crawford <scrawford@pinpointresearch.com>)
List pgsql-hackers
Yeah, why bother. Even ’native’ encryption/SSL in PG (were one to use it ‘natively’, as we do) is so good; adding yet another layer seems overkill…

Lou Picciano

On Oct 9, 2019, at 6:39 PM, Steve Crawford <scrawford@pinpointresearch.com> wrote:


On Wed, Oct 9, 2019 at 12:56 PM Timmy Siu <timmy.siu@aol.com> wrote:
Dear all postgresql developers,

I have tested postgres v11 against TCP Wrappers but it does not respond
to TCP wrappers port blocking.

May I suggest the community to have postgres to work with TCP wrappers.??
Its security will be better.


The last stable release of TCP Wrappers was a couple decades ago. It's deprecated in RHEL7 and removed in RHEL8.  I'm not a PG core member or anything but rather doubt that's an area where the developers will want to expend effort.

Cheers,
Steve


pgsql-hackers by date:

Previous
From: Steve Crawford
Date:
Subject: Re: TCP Wrappers
Next
From: "Smith, Peter"
Date:
Subject: RE: Proposal: Add more compile-time asserts to exposeinconsistencies.