News for hackers. Stuff that matters.

A comment on Reclaiming IPv4 Class E's 240.0.0.0/4. Parent comment

Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by bell-cot on Monday May 27, 2024 @12:36PM (#40492339)
An org with that level of technical control might well be an extremely security-conscious org. And "No IPv6 Anywhere, Ever" would make it somewhat easier to keep things secure.
[ Parent | on HN ]
Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by phildenhoff on Monday May 27, 2024 @01:18PM (#40492724)
Ah, for the companies with high technical control, but no technical competence! Of course :)
[ Parent | on HN ]
Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by bell-cot on Monday May 27, 2024 @01:43PM (#40492935)
If your #1 goal is to keep the stuff you manage secure, then keeping that stuff as simple as practical is a pretty obvious strategy.

If your #1 goal is to keep your 133t bragging rights, then there are no such things as unnecessary nor excessive complexities.

[ Parent | on HN ]
Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by zokier on Monday May 27, 2024 @04:31PM (#40494392)
A brick is very simple and very secure. Some might say practically unhackable.
[ Parent | on HN ]
Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by bell-cot on Monday May 27, 2024 @07:22PM (#40495745)
True. But if you need a secure network for the factory's SCADA equipment - a brick is just not a practical substitute.
[ Parent | on HN ]