21
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Jan 2025
21 points (76.9% liked)
Linux
6067 readers
290 users here now
A community for everything relating to the GNU/Linux operating system
Also check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
the narrative shaping in american media is so disgusting; they won't even question whether or not my government's expanded export controls in kicking out some of its most prolific contributors simply because they're russian is a factor and cover it up by counting the number of lines added.
what happens next year or the year after that? are the same contributors expect to keep working at the same scale they're doing now? the youngest ones are in their 40's and paid exorbitantly well; what happens when they retire? do we all just switch to bsd?
Nobody was kicked out for simply being Russian. People were kicked out because they work for sanctioned organizations.
The whole point of open source was that you can see the code and the commits. We don't need to trust anybody. I feel like banning contributors is just contradicting one of the key benefits of open source.
Wouldn't it be the right thing to just improve the security and vetting of commits to the kernel? After all, it's the Linux Kernel.
Besides, the idea that employed developers with a Russian day job are a risk... but one fails to consider these were the honest ones who declared their day job. Does the threat modelling end there?
What would you do about people who... lie online about where they work? (I know it's impossible but bear with me).
I feel like properly vetting commits to the kernel that does not involve the core contributors and maintainers too much is the way to go. (Tests, dedicated resources, more time in review, commit to a staging branch and ask the world's foremost hackers to find vulnerabilities, etc)
You are misunderstanding why the sanctions happened. It has nothing to do with whether or not the individuals working at those entities are trustworthy or not.
The Linux Foundation is an institute of the United States. The United States has demanded that entities within their jurisdiction, like the Linux Foundation, follow sanctions, and cut contact and interaction with sanctioned entities.
Because the Linux Foundation doesn't want to be punished or pay fines, they follow those sanctions. Nothing to do with trusting the individual contributors or corporations.
This is probably what happened. The contributors went home, to their personal emails, and the world kept spinning and no one looked twice.
Source: https://lwn.net/ml/all/CAHk-=whNGNVnYHHSXUAsWds_MoZ-iEgRMQMxZZ0z-jY4uHT+Gg@mail.gmail.com/
Reviewing every change and discovering every issue is unfeasible on multiple levels. Even skipping that fundamental, base level requirement; you need to trust in trustworthiness from submitters and reviewers, and that people review. You need to trust those maintainers that can push and pull and merge. You need to trust the builders and publishers and distributors.
I doubt you're reviewing every code change and compiling or verifying reproducible builds on every software and patch version you run. You put trust in the chain. And the chain decided to cut at some point because of risk.
So you think people do only one job and have only one concern? Do you think people of sanctioned countries, contributing to an unjust war, more or less directly, are a bad place to start reducing risks?
I'm baffled you can make this point while at the same time not accepting their decision after review, assessment, and consequence. You're asking them to review while not accepting their decision. From the same people.