DigitalDilemma

Absolutely.

These services are also used by many governments around the world and considered critical infrastructure.

Terrifying, right?

Canonical is UK based, so scrub that.

But Redhat, Rocky, Alma are all owned by US legal entities and can absolutely be legally forced to do as you describe.

Technically blocked is something else, mind. We’re clever, resourceful and motivated people and US laws wouldn’t directly affect us.

However - you’re thinking small. US influence of IT is massive. Routers, servers, hardware of all levels. The most enterprise level software is US led. All of these things can be restricted, or tarriffed heavily, or sanctioned entirely. If the US wants to hurt the rest of the world, it just has to tell Broadcom to turn off vmware outside of America. Ditto Cisco, Ditto Dell, Ditto… etc etc. Sure, it would be illegal, but does the American government care about that?

Anyone telling you that “Y won’t happen because it’s unthinkable” clearly hasn’t been paying attention this year.

I have a saying, “If it’s not DNS, then it’s Selinux”. It blocks stuff so frequently it’s a major time sink for us.

It is overly complex and difficult to understand, especially if you’re developing and deploying software that does not have correct pre-rolled policies. A regular job for me is to help developers solve this - which generally means running their service, seeing what Selinux blocks on, and then applying a fix. Repeat 2-8 times until every way Selinux is trying to access a file is explicitly allowed. And sometimes, even software that comes via official repos has buggy selinux policies that break things.

Fortunately, there are tools to help you. Install setroubleshooter amd when something doesn’t work, “grep seal /var/log/messages” and if it’s selinux causing the problem, you’ll find instructions showing you what went wrong and how to create an exception. I absolutely consider this tool essential when using any system with selinux enabled.