redis-docker VS masscan

version: "3.7" services: postgres: image: "postgres:14-alpine" environment: POSTGRES_USER: "example" POSTGRES_PASSWORD: "example" ports: - "5432:5432" volumes: - "postgres:/var/lib/postgresql/data" redis: image: "redis:5-alpine" command: ["redis-server", "--requirepass", "yourpassword", "--appendonly", "yes"] healthcheck: test: ["CMD", "redis-cli", "ping"] interval: 10s timeout: 5s retries: 5 ports: - "6379:6379" volumes: - redis:/data sysctls: # https://github.com/docker-library/redis/issues/35 net.core.somaxconn: "511" sidekiq: depends_on: - "postgres" - "redis" - "elasticsearch" build: context: . args: environment: development image: you/yourapp command: bundle exec sidekiq -C config/sidekiq.yml.erb volumes: - ".:/app" # don"t mount tmp directory - /app/tmp env_file: - ".env" web: build: context: . args: environment: development image: you/yourapp command: bundle exec rspec depends_on: elasticsearch: condition: service_healthy postgres: condition: service_started redis: condition: service_healthy tty: true stdin_open: true ports: - "3000:3000" env_file: - ".env" elasticsearch: container_name: elasticsearch image: docker.elastic.co/elasticsearch/elasticsearch:7.4.2 environment: - discovery.type=single-node - cluster.name=docker-cluster - bootstrap.memory_lock=true - "ES_JAVA_OPTS=-Xms1024m -Xmx1024m" - "logger.org.elasticsearch=error" healthcheck: test: curl --fail elasticsearch:9200/_cat/health >/dev/null || exit 1 interval: 30s timeout: 10s retries: 5 ulimits: memlock: soft: -1 hard: -1 volumes: - esdata:/usr/share/elasticsearch/data ports: - 9200:9200 volumes: redis: postgres: esdata:

I was caught out by this too[0]. I now have a fw script which runs automatically for demos etc.

[0] https://github.com/docker-library/redis/issues/259#issuecomm...

Short hack: As seen in m a n y Dockerfiles, the apt cache is located at /var/lib/apt/lists.

Can I get banned for mass scanning with https://github.com/robertdavidgraham/masscan or does it slow down any other vms from other persons?

Nope, this doesn't work any more. Shodan checks all ports (so any attackers using data from Shodan already know which ports you have open), and tools like masscan (https://github.com/robertdavidgraham/masscan) let you portscan the entire IPv4 address space in less than 10 minutes.

https://github.com/LogoiLab/mcsl https://github.com/robertdavidgraham/masscan

Changing the default port does nothing for security. It only prevents some basic brute force or default password scripts. Anyone is able to scan for it in no time anyway (https://github.com/robertdavidgraham/masscan).

But it should blow away the far-too-common belief that no-one's after you because you're not interesting enough. IPv4 is smaller than we think. It is not difficult to scan the entire ipv4 space in minutes. And every single one of those is going to knock your door on the way past.

I'm not sure about the article, but the blazingly-fast IP scanner sounds a lot like Masscan. It can scan the entire Internet in 5 minutes and has received a lot of press: https://github.com/robertdavidgraham/masscan . https://rushter.com/blog/how-masscan-works/ is one of many articles about it.

Here's an except from the masscan docs: