search for: 6f11fc41d2f0

Displaying 5 results from an estimated 5 matches for "6f11fc41d2f0".

PostgreSQL port accessible even though it should be blocked by firewall
2018 Oct 29
4
PostgreSQL port accessible even though it should be blocked by firewall
.../tcp open ssh 5432/tcp open postgresql Nmap done: 1 IP address (1 host up) scanned in 57.26 seconds $ PostgreSQL is running in a docker container: $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 6f11fc41d2f0 postgres "docker-entrypoint..." 4 days ago Up 4 days 0.0.0.0:5432->5432/tcp postgres $ The various docker interfaces and virtual bridges are not assigned to any specific zone. Why is port 5432/tcp open? frank
PostgreSQL port accessible even though it should be blocked by firewall
2018 Oct 30
1
PostgreSQL port accessible even though it should be blocked by firewall
...ommen <list.centos at drosera.ch> wrote: >> >> PostgreSQL is running in a docker container: >> >> $ docker ps >> CONTAINER ID IMAGE COMMAND >> CREATED STATUS PORTS NAMES >> 6f11fc41d2f0 postgres "docker-entrypoint..." 4 >> days ago Up 4 days 0.0.0.0:5432->5432/tcp postgres >> $ >> >> The various docker interfaces and virtual bridges are not assigned to >> any specific zone. >> >>...
PostgreSQL port accessible even though it should be blocked by firewall
2018 Oct 29
0
PostgreSQL port accessible even though it should be blocked by firewall
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????????????????? "docker-entrypoint..."?? 4 > days ago????????? Up 4 days?????????? 0.0.0.0:5432->5432/tcp?? postgres > $ > > > The various docker interfaces and virtual bridges are not assigned to > any specific zone. > > > Why is port...
PostgreSQL port accessible even though it should be blocked by firewall
2018 Oct 29
0
PostgreSQL port accessible even though it should be blocked by firewall
On 2018-10-29, Frank Thommen <list.centos at drosera.ch> wrote: > > PostgreSQL is running in a docker container: > > $ docker ps > CONTAINER ID IMAGE COMMAND > CREATED STATUS PORTS NAMES > 6f11fc41d2f0 postgres "docker-entrypoint..." 4 > days ago Up 4 days 0.0.0.0:5432->5432/tcp postgres > $ > > The various docker interfaces and virtual bridges are not assigned to > any specific zone. > > Why is port 5432/tcp open?...
PostgreSQL port accessible even though it should be blocked by firewall
2018 Oct 30
2
PostgreSQL port accessible even though it should be blocked by firewall
...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 >> 6f11fc41d2f0??????? postgres????????????????? "docker-entrypoint..." >> 4 days ago????????? Up 4 days?????????? 0.0.0.0:5432->5432/tcp?? postgres >> $ >> >> >> The various docker interfaces and virtual bridges are not assigned to >> any specific zone. >&gt...