Skip Navigation

Did the recent Linux drama change your views on how you perceived Open Source projects?

I for one am going through quite a culture shock. I always assumed the nature of FOSS software made it immune to be confined within the policies of nations; I guess if one day the government of USA starts to think that its a security concers for china to use and contribute to core opensource software created by its citizens or based in their boundaries, they might strongarm FOSS communities and projects to make their software exclude them in someway or worse declare GPL software a threat to national security.

125 comments
  • It wasn't a culture shock but it made something obvious that sometimes gets forgotten. The "Open" just means that one can look at the source code and copy it to make a new version. There is no obligation of the original creators to support things outside of what they want/can do.

  • It just shows how hypocritical and Western biased the community is. Are Israeli and US maintainers ever going to get kicked out of projects for their countries many crimes? No of course not, they would never apply their own standards to themselves, which defeats the point of them in the first place.

  • Not really, open source projects don't necessarily have to be open to all contributors and I was aware of this already. They have to be open to anyone doing what they want with the code, by definition, which is good, but they don't have to allow everyone to contribute to upstream. I'm not sure if there's any particular defence against this being used in a discriminatory manner, but I do think this effect is significantly mitigated by the decentralised nature of open source and the fact that it's not too uncommon for forks to become preferred over the original, the fact that open source projects rise and fall in popularity, etc.

    I wonder if there's some way to manage an open source project so that it's not subject to particular national laws in this way.

  • Is this really Linux drama though? It seems more like political drama that ended up jizzing on Linux.

    I mean, yeah, there's been drama after the decision was made based on legal issues brought about by political drama, but this part of it isn't, if you get the distinction.

    The only real linux drama part, as far as I can see is the crappy way it was announced, which isn't what most of the people involved in the drama after the fact are complaining about.

    I dunno, I'm not complaining about the post here, just talking about the overall issue itself using the post as a jumping point.

    Anyway, I guess what I'm getting at is that foss development can't be immune from political fuckery (no matter how justified or unjustified it is). Everyone that's going to be involved in development is going to live under some nation's thumb, and is vulnerable to any legal ramifications of that nation. So there's no way to prevent a project being strongarmed; all that's possible is having enough people that can review the code do so, so that any fuckery that affects the project is known, so that everyone can decide what they want to do about it as individuals.

    As long as individual people have the ability to use any foss software they want on their own devices, there's a limit to how bad the fuckery can get. Tbh, I'm more worried about corporate fuckery in foss projects than governmental

  • Well, in theory open source is immune to all that. However, the country a project is registered at, matters. That's why the RISC-V project, for example, took its headquarters from the US to Switzerland. For that exact reason: so no country could strong arm it, especially since Chinese were the major contributors to the project (Switzerland is not 100% neutral, but it's more neutral than other countries).

  • What happened this time?

    Edit, answered elsewhere:

    Recently, Linux removed several people from their organization that have Russian email addresses. Linus made a statement that confirmed this was done intentionally. I believe that there was some mention of following sanctions on Russia due to the war. I haven’t looked into the details of it all, so take my analysis with a grain of salt. From what I understand, it sounded like it was only Russian maintainers that were removed and normal users submitting code from Russia can still contribute. Maintainers have elevated permissions and can control what code gets accepted into a project, meaning that a bad actor could allow some malicious code to sneak past. This may have also contributed to the decision since this type of attack has happened before and Russia seems like a likely culprit. The reactions to this change have been varied. Some people feel it is somewhat justified or reasonable, some people think that it means it is no longer open source, and some people think it is unfairly punishing Russian civilians (it is worth noting that that is part of the point of sanctions).

  • I think the prestige of "maintainers" and contributions/control are what is being torn down. Anyone anywhere is still welcome to contribute, they are simply limited from direct control. They can still fork at any time, anyone can. Getting people to follow your fork is another thing entirely, and your open source code will still likely be incorporated directly or indirectly. The only thing that has changed is the misguided prestige that has grown around the project and is not a required or relevant part of the project as a whole.

  • From what I understand this wasn't a decision dictated by sanctions nor was there any strongarming. Otherwise it would've happend way earlier.

    I also think splitting politics and literally anything else doesn't work and is something people who benefit from the discussion (or lack therof) made up.

  • If you are having sensitive information stored using closed-source software/OS, you can stop reading right here. This is your biggest vulnerability and the best thing you can do is to switch to FOSS.

    For those that have already switched:
    It made me think about how to improve the resistance of large FOSS projects against state-sponsored attackers injecting backdoors.

    The best thing i came up with would be to have each contribution checked by a contributor of a rival state. So a Russian (or Chinese) contributor verifies a contribution by an American.
    The verifying contributors would have to be chosen at random in a way that is not predeterminable by an attacker, otherwise a Chinese-state contributor will contribute harmless code until the next verifier will be a US-based Chinese spy. Then they will submit a backdoor and have it checked by an American citizen paid by China.
    Also the random number generator has to be verifiable by outsiders, otherwise a spy in the Linux-Foundation can manipulate the outcome of choosing a favorable verifier for a backdoor.

    This can obviously only be done as long as there are lots of contributors from rivaling states. If the US decided that Linux can only allow contributors from USA/EU, then this model can not work and Linux would have to relocate into a more favorable state like Switzerland.

    What one should keep in mind that even if the US would ban all foreign contributions and the foundation would not relocate, Linux would still be more secure than any closed source OS, as those foreigners can still look at the code and blow the whistle on bugs/backdoors. It would however be much more insecure than it is now, as the overhead for finding bugs/backdoors would be much larger.

125 comments