That seems like an awfully biased headline for what they’re reporting as essentially “he said she said”.

A Thai military official said that the airstrikes were retaliation for an attack earlier on Monday that killed a Thai soldier.

Cambodia’s Ministry of National Defense denied the RTAF allegations, calling it “false information” in a statement on X.

I’m admittedly biased here but one of these statements feels awfully familiar

The countries were at peace before something caused them to escalate into a war. You can't just declare that a war has ended by having a representative from each side sign a piece of paper and expect it to remain this way without addressing the root causes that lead to said war to begin with.

But trying to understand the situation and finding ways to address those root causes requires far more work than Trump can be bothered with. He only cares about giving the impression that he did something.

As usual, Trump has an overly simplistic view of the problem to match his abysmal level of understanding of it, and proposes equally simplistic solutions to it. He then declares he fixed it because of how much of a genius he is and then ignores the evidence that it didn't work.

NBC's AI can't write worth a hoot:

Hundreds of works were damaged at the Louvre in Paris when a pipe burst because of flooding, the museum’s deputy general administrator said.

The flooding led to a burst pipe and affected one of the three rooms of the library in the Egyptian antiquities department, he said.

Above are paragraphs 1 and 3 from the referenced article.

A simple but logical reading of both states that "a flood occurred (first), and the flood is what caused the pipe to burst (second)". Extremely disappointed in this level of journalistic competence.

In an enterprise setting, you shouldn't trust the server firewall. You lock that down with your network equipment.

Edit: sorry, I failed to read the whole post 🤦‍♂️. I don't have a good answer for you. When I used docker in my homelab, I exposed services using labels and a traefik container similar to this: docs.docker.com/guides/traefik…

That doesn't protect you from accidentally exposing ports, but it helps make it more obvious when it happens.

HTTP routing with Traefik

"Use Traefik to easily route traffic between multiple containers or non-containerized workloads"

^{Docker Documentation}

I use podman instead, though I'm honestly not certain this "fixes" the problem you described. I assume it does purely on the no-root point.

Agreeing with the other poster, network tools and not relying on the server itself is the professional fix

If you are good at manipulating iptables there is a way around this

Modern systems shouldn't be using iptables any more.

this is the second time I've seen a post like this.

docker has always been like this. if it's news to you then you must be new to docker.

if you're using the built in firewall to secure your system on your wan, you're doing it wrong. get a physical firewall. if you're doing it to secure your lan then you just need to put in some proper routes and let your hardware firewall sort it out with some vlans.

don't rely on firewalld or iptables for anything.

If there's a port you want accessible from the host/other containers but not beyond the host, consider using the expose directive instead of ports. As an added bonus, you don't need to come up with arbitrary ports to assign on the host for every container with a shared port.

IMO it's more intuitive to connect to a service via container_name:443 instead of localhost:8443

I basically just avoid exposing ports from containers unless I really do want them exposed on the host?

Most services go through my reverse proxy, traefik.

Things like databases don't publish ports on the host because they're only accessed internally, using their container name.

How I sleep knowing Fedora + podman actually uses safe firewalld zones out of box instead of expecting the user to hack around with the clown show that is ufw.

I could be wrong here but I feel like the answer is in the docs itself:

If you are running Docker with the iptables or ip6tables options set to true, and firewalld is enabled on your system, in addition to its usual iptables or nftables rules, Docker creates a firewalld zone called docker, with target ACCEPT.

All bridge network interfaces created by Docker (for example, docker0) are inserted into the docker zone.

Docker also creates a forwarding policy called docker-forwarding that allows forwarding from ANY zone to the docker zone.

Modify the zone to your security needs? Or does Docker reset the zone rules ever startup? If this is the same as podman, the docker zone should actually accept traffic from your public zone which has your physical NIC, which would mean you don't have to do anything since public default is to DROP.

So, this discussion has intrigued me and some good points have been brought up by seemingly knowledgeable network engineers of which I am not. If I may, introduce you guys to my network to see if there are points I can improve on.

For simplicity, the network diagram would be: modem---->stand alone pfsense firewall with a tailscale overlay, running Suricata, pfblockerng, vlans to segment server traffic from normal traffic, & a very robust rule set & ntopng for traffic analysis -----> server & devices. Server is piped through Cloudflare Tunnel/Zero Trust. On the server, I run UFW, fail2ban with a hair trigger & Crowdsec. Also, since I am the only user, I lock everything down in the .host Allow/Deny & use ssh keys. Users cause complexities and complexities turn into issues. All devices are running a VPN. I do run Docker in lieu of Podman. Server has been hardened through various means and to an extent in line with Lynis.

I've been told that this is overengineered, but it seems to work just jammy. Knock on wood, I've never had a breach on my local network, though there is always the possibility. A long time ago, when I stood my first server up on a VPS, it got hacked almost immediately. So I dropped back and did some studying, but I am no network engineer.

Anyways, for the experts here, my question is: What would you do to improve, harden, rip out, redo, add etc?

ETA: Server also has a tailscale overlay.