News for hackers. Stuff that matters.
Re:DDoSecrets publishes 410 GB of heap dumps, hacked from Te... by teekert on Tuesday May 20, 2025 @05:11AM (#44039453)
Imaging putting up a firewall to mitigate this, then docker compose helpfully opening the ports for you. Security comes in layers.
Re:DDoSecrets publishes 410 GB of heap dumps, hacked from Te... by callamdelaney on Tuesday May 20, 2025 @09:51AM (#44041701)
This feature of docker compose is insane.
Re:DDoSecrets publishes 410 GB of heap dumps, hacked from Te... by teekert on Tuesday May 20, 2025 @01:57PM (#44044148)
Right!? I learned with a colleague: Didn’t you restrict everything to the Tailnet? Yes, feel free to check UFW. Hmm, then why does nmap show all this stuff when scanning from the lan? Wtf??
Re:DDoSecrets publishes 410 GB of heap dumps, hacked from Te... by callamdelaney on Thursday May 22, 2025 @06:54AM (#44060781)
Similar here, UFW setup to only enable access via Caddy to our http services - wait, why can I connect directly to our redis instance?

Took a while to workout that for some reason docker-compose is messing directly with iptables to shoot holes in the firewall we'd configured. Figured out you have to write your compose in some super special way to disable that functionality. Compose should never ever open network ports, ever in my book - to do so without a warning or anything though is like I said, insane!