| From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
|---|---|
| To: | Timmy Siu <timmy(dot)siu(at)aol(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: TCP Wrappers |
| Date: | 2019-10-09 22:39:11 |
| Message-ID: | CAEfWYyyFZEYo9pEBPbVB7PRmdacxj1=+ah4h4Gb0N2U2F8-Zkw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 9, 2019 at 12:56 PM Timmy Siu <timmy(dot)siu(at)aol(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-10-09 22:46:38 | Re: pg_dump compatibility level / use create view instead of create table/rule |
| Previous Message | Tom Lane | 2019-10-09 22:26:58 | Re: Missed check for too-many-children in bgworker spawning |