3 ms·
What surprises me most is the machine running Docker was 100% connected directly to a public network interface. That’s the real root of the problem here.
by whalesalad 5y ago
What surprises me most is the machine running Docker was 100% connected directly to a public network interface. That’s the real root of the problem here.
- tedk-42 5y agoExactly - and there's no mention either of how the fix was implemented nor what remediations were done to prevent it happening again in the future...
- alexchamberlain 5y agoThere's a section st the end detailing 3 fixes, including using a private network.
- fulafel 5y agoAmbiguous addresses are generally a pretty big headache and have a lot of security downsides, network level firewalls are better and would have worked here too. It's literally the old NAT vs firewall case.