On Tue, 21.07.15 16:39, Florian Weimer (fwei...@redhat.com) wrote:
On 07/21/2015 01:52 PM, David Herrmann wrote:
Hi
On Tue, Jul 21, 2015 at 1:37 PM, Florian Weimer fwei...@redhat.com wrote:
We have quite a zoo of services which listen on localhost, on a fixed
TCP port, for use by
On Tue, 21.07.15 13:37, Florian Weimer (fwei...@redhat.com) wrote:
We have quite a zoo of services which listen on localhost, on a fixed
TCP port, for use by local clients. The canonical example is PostgreSQL
on 5432/TCP, for the benefit of Java clients (which cannot use the UNIX
domain
We have quite a zoo of services which listen on localhost, on a fixed
TCP port, for use by local clients. The canonical example is PostgreSQL
on 5432/TCP, for the benefit of Java clients (which cannot use the UNIX
domain socket). This has the obvious issue that if a local attacker
crashes the
Hi
On Tue, Jul 21, 2015 at 1:37 PM, Florian Weimer fwei...@redhat.com wrote:
We have quite a zoo of services which listen on localhost, on a fixed
TCP port, for use by local clients. The canonical example is PostgreSQL
on 5432/TCP, for the benefit of Java clients (which cannot use the UNIX
On 07/21/2015 01:52 PM, David Herrmann wrote:
Hi
On Tue, Jul 21, 2015 at 1:37 PM, Florian Weimer fwei...@redhat.com wrote:
We have quite a zoo of services which listen on localhost, on a fixed
TCP port, for use by local clients. The canonical example is PostgreSQL
on 5432/TCP, for the
