Linux kernel bans Russian developers amid compliance rules

Linux kernel excludes Russian developers: politics enters code

The Linux kernel, the core of the operating system powering much of the internet, mobile devices, and servers worldwide, has stopped accepting contributions from developers linked to Russia. The decision, executed by Linus Torvalds himself, relies on what the text calls "compliance requirements" derived from international sanctions. It is not a technical patch. It is a purge with a signature.

The news, published by The Register, includes Torvalds' response to those asking for the measure to be reversed: "Ok, lots of Russian trolls out and about," he wrote, adding "Use whatever mush you call brains. I'm Finnish." The kernel founder, a Finnish-American citizen, does not bother to hide his stance. The community has been divided for days between those who see a legal obligation and those who view it as yielding to political pressure.

What exactly peine with Russian developers

The trigger was the expulsion of several maintainers of Russian origin from the kernel development process. The measure does not affect already published code —Linux is free software and anyone can download, audit, and modify it— but it does affect who can propose changes that enter the official branch. In practice, Moscow loses influence over the technical direction of critical infrastructure.

Some argue that Torvalds acts out of legal obligation: Western sanctions against Russia require companies and foundations funding the kernel to filter who signs the code. Counter-arguments suggest that Torvalds turned the measure into a political statement, mixing regulatory compliance with insults toward dissenters. The Finnish developer's response —"it will not be reverted"— closes the door to any negotiation.

The underlying technical debate is uncomfortable: if the kernel is open, why does it matter who signs it? The short answer is that it matters for traceability. The long answer is that it matters for control. And that control, in a project moving billions in infrastructure, is never just technical.

SELinux and the fox guarding the henhouse: an argument that fails

The message opening the issue poses an uncomfortable question: SELinux, the kernel security module, was created by the NSA. Are we putting the fox in charge of the hens? The material's own answer is nuanced: since it is free software, everything the kernel does is public and auditable. Any backdoor would be detectable by thousands of independent eyes.

That does not miccionan risks do not exist. An analyst within the material summarizes it bluntly: "Only the good programmer knows what their code does. They can slip a backdoor right under your nose." Auditing works as deterrence, not as absolute guarantee. And modern hardware —Intel's ME/AMT, UEFI— adds opaque layers that no kernel can fully control.

The discussion then shifts to the complete ecosystem. One participant argues that "80% of commercial VPNs are controlled by Israelis." Another points out that using any device connected to the internet means using technology developed in the United States. The implicit conclusion is that total technological sovereignty does not exist; only different degrees of dependency.

FreeBSD, Tails, and the alternatives being considered

The conversation turns to alternatives. FreeBSD appears several times as a more "consistent" and less politicized option, although with a serious driver problem: "You have to buy recommended hardware, otherwise it doesn't work." Tails, the privacy-focused system, is mentioned as a practical tool. And some claim that the kernel's open nature allows downloading a clean version and compiling it oneself.

The underlying problem is another: mass adoption. One message states plainly: "when a platform fills with people, it rots." The massive influx of users and political agendas into projects that started as engineering niches has changed the rules. What was once decided by technical merit is now partly decided by compliance criteria, corporate fruta, and geopolitical pressure.

Context: Finland, NATO, and the 1,300-kilometer border

Torvalds' nationality is not a minor detail. Finland shares a 1,300-kilometer border with Russia and joined NATO, dismantling the argument that Moscow attacked Ukraine to prevent the Alliance from reaching its borders. That fact, present in the material, explains why a Finn responds with such harshness to accusations of yielding to pressure.

The issue fits into a broader technological war. BRICS nations have long demanded digital sovereignty; the kernel measure gives them an argument. If free software stops being neutral, the alternative is building one's own. And that is not good news for those currently controlling the infrastructure.

What might happen next with the Linux kernel

The most repeated prediction in the material is that there will be two kernel branches: the Western one and the BRICS countries' one. It is not an absurd hypothesis. Ideological forks already exist —debates over renaming "master/slave" or rejecting contributions for lack of profile pronouns— and this would be another, with the difference that states are involved here.

The open question remains whether open source can survive as a neutral space when geopolitics cuts through it. As of this discussion, the answer is that it cannot entirely. The kernel will remain auditable. But the entry gate to the kernel is no longer open to everyone.