MQTT without authentication

Community Containers
1

Exactly my sense of humour :wink:

grafik
grafik957×106 4.65 KB

While scanning my Greenbone server running the latest Community Containers I get the above result. I’m using the default configuration/docker-compose file from greenbone.github.io

Is there a way to secure the MQTT access?

Best regards

Christian

1 Like
2

I had a laugh as well :slight_smile:

You can safely disable the port directive for the MQTT server if you’re running everything on one host, I guess. At least that is what I did.

1 Like
3

Could you explain how to resolve this issue?
I am using GCE docker version.

4

I came across this issue, too a couple of days ago when testing an all in one docker host deployment which should be placed outside of our corporate firewall.

I’m also very interested how to solve this issue.

5

Basically just remove the public port in the mqtt broker:

  mqtt-broker:
    restart: on-failure
    image: greenbone/mqtt-broker
    ports:
      - 1883:1883
    networks:
      default:
        aliases:
          - mqtt-broker
          - broker

to

  mqtt-broker:
    restart: on-failure
    image: greenbone/mqtt-broker
    networks:
      default:
        aliases:
          - mqtt-broker
          - broker
1 Like
6

Why was the port in the configuration or what is the port needed for in Greenbone?

7

I’m just guessing, but could be for a distributed cluster setup.

8

Perhaps someone at Greenbone can help and tell us for what this port is used and if it can safely disabled in an all in one docker environment.

9

@sven1
Is a distributed cluster setup possible with the community edition?

@bellum
Yes, an explanation is of course good.

A note should be added to the doc for a secure configuration.

10

Just remove that statement. It’s not necessary. I think it’s just in there by accident.

2 Likes