On Thu, 10 Oct 2019 at 07:15, Tom Lane wrote:
>
> That doesn't bode well for the number of people who would use or care
> about such a feature.
>
Agreed. tcp_wrappers predates the widespread availability of easy,
effective software firewalls. Back when services listened on 0.0.0.0 and if
you we
Steve Crawford writes:
> On Wed, Oct 9, 2019 at 12:56 PM Timmy Siu wrote:
>> 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
> deprecat
:timmy@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
On Wed, Oct 9, 2019 at 12:56 PM Timmy Siu 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.??
>
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.
Regards,
Timmy