Re: [CentOS] PostgreSQL port accessible even though it should be blocked by firewall

2018-11-01 Thread Frank Thommen
On 31/10/18 18:32, Gordon Messmer wrote: On 10/30/18 8:31 AM, Frank Thommen wrote: I am still puzzled that it is possible to circumvent firewalld so easily.  Basically it means, that firewalld is not to be trusted as soon as containers with port forwarding are running on a system. It's hard

Re: [CentOS] PostgreSQL port accessible even though it should be blocked by firewall

2018-10-31 Thread Gordon Messmer
On 10/30/18 8:31 AM, Frank Thommen wrote: I am still puzzled that it is possible to circumvent firewalld so easily.  Basically it means, that firewalld is not to be trusted as soon as containers with port forwarding are running on a system. It's hard to see this as a security or trust

Re: [CentOS] PostgreSQL port accessible even though it should be blocked by firewall

2018-10-30 Thread mark
Frank Thommen wrote: > On 10/29/2018 08:43 PM, Keith Keller wrote: > >> On 2018-10-29, Frank Thommen wrote: >> >>> >>> PostgreSQL is running in a docker container: >>> >>> >>> $ docker ps >>> CONTAINER IDIMAGE COMMAND >>> CREATED STATUS

Re: [CentOS] PostgreSQL port accessible even though it should be blocked by firewall

2018-10-30 Thread Frank Thommen
On 10/29/2018 08:43 PM, Keith Keller wrote: On 2018-10-29, Frank Thommen wrote: PostgreSQL is running in a docker container: $ docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES 6f11fc41d2f0

Re: [CentOS] PostgreSQL port accessible even though it should be blocked by firewall

2018-10-30 Thread Frank Thommen
On 10/29/2018 08:18 PM, Alexander Dalloz wrote: Am 29.10.2018 um 20:03 schrieb Frank Thommen: PostgreSQL is running in a docker container: $ docker ps CONTAINER ID    IMAGE COMMAND CREATED STATUS  PORTS    NAMES

Re: [CentOS] PostgreSQL port accessible even though it should be blocked by firewall

2018-10-29 Thread Keith Keller
On 2018-10-29, Frank Thommen wrote: > > PostgreSQL is running in a docker container: > > $ docker ps > CONTAINER IDIMAGE COMMAND >CREATED STATUS PORTSNAMES > 6f11fc41d2f0postgres

Re: [CentOS] PostgreSQL port accessible even though it should be blocked by firewall

2018-10-29 Thread Alexander Dalloz
Am 29.10.2018 um 20:03 schrieb Frank Thommen: PostgreSQL is running in a docker container: $ docker ps CONTAINER ID    IMAGE COMMAND CREATED STATUS  PORTS    NAMES 6f11fc41d2f0    postgres 

[CentOS] PostgreSQL port accessible even though it should be blocked by firewall

2018-10-29 Thread Frank Thommen
Hi, this puzzles me: On one of our developer workstations, all ports with the exception of SSH are closed: $ firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: eno1 sources: services: ssh dhcpv6-client ports: 22/tcp protocols: