Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Linux

Linus Torvalds Comments On The Russian Linux Maintainers Being Delisted (phoronix.com) 203

Ancient Slashdot reader szo shares a report from Phoronix: Quietly merged into this week's Linux 6.12-rc4 kernel was a patch that removes a number of kernel maintainers from being noted in the official MAINTAINERS file that recognizes all of the driver and subsystem maintainers. [...] [Greg Kroah-Hartman who authored the patch] simply commented in there: "Remove some entries due to various compliance requirements. They can come back in the future if sufficient documentation is provided." [...] The commonality of all these maintainers being dropped? They appear to all be Russian or associated with Russia. Most of them with .ru email addresses. Linux creator Linus Torvalds has since commented on the situation: Ok, lots of Russian trolls out and about. It's entirely clear why the change was done, it's not getting reverted, and using multiple random anonymous accounts to try to "grass root" it by Russian troll factories isn't going to change anything. And FYI for the actual innocent bystanders who aren't troll farm accounts - the "various compliance requirements" are not just a US thing.

If you haven't heard of Russian sanctions yet, you should try to read the news some day. And by "news," I don't mean Russian state-sponsored spam. As to sending me a revert patch - please use whatever mush you call brains. I'm Finnish. Did you think I'd be *supporting* Russian aggression? Apparently it's not just lack of real news, it's lack of history knowledge too.

This discussion has been archived. No new comments can be posted.

Linus Torvalds Comments On The Russian Linux Maintainers Being Delisted

Comments Filter:
  • by Gravis Zero ( 934156 ) on Wednesday October 23, 2024 @06:44PM (#64888883)

    This isn't just for the protection of the world but it's also to protect the maintainers from government "influence" as well. I know that not all Russians support their government's actions so potentially putting them in the position of becoming pawn for said government is unethical. However, if they do support their government's actions then they may be tempted to to be a willing agent for said government. In both cases, it's best to not put them in a potentially compromising position.

    • Re: (Score:2, Offtopic)

      by sg_oneill ( 159032 )

      I do kinda feel for russians who arent happy about this. Early in the invasion there was a lot of , particularly millenial and gen z russians who seemed genuinely distressed about it, but where freaked out by the prospect of protesting. At least one told me they knew a guy who was organizing protests and just disappeared one day. She hoped he was just laying low, but didnt know.

      This is why rather than funding ukranian armaments, something I'm pretty uncomfortable with (not opposed, just uncomfortable) I put

      • Re: (Score:2, Offtopic)

        There are places that you can donate that purchase equipment other than weapons, including humanitarian supplies. Be careful about where your money goes, as there are also some fraudulent groups out there. But lots of groups are doing good work that doesn't involve weapons.

      • by keltor ( 99721 ) *
        I know lots of Russians who were 100% unhappy about everything, and this just pushes them further into their personal efforts to move their parents/immediate family out of Russia and to "wherever" they are living.
    • by Cito ( 1725214 )

      I don't quite understand why this has gotten more "noise" when after the attack last October they pretty much did the same for any code pushed or reverts from Palestinians although they made the same exceptions for unblocking with "sufficient documentation provided" as was also stated in this article. There was zero posts on Slashdot about that when it happened, although there was one on news.ycombinator that had some people upset and making a lot of the same arguments that people now are making in support

    • This argument (we need to protect the world from our enemies du jour) works for closed source but is not needed for open source. In a true open source community, there are eyeballs which look at the code and point out bad sections. And commits get accepted in the open and only after verification. Trust in the personal motivations of the original authors of the code is not needed.

      I think what you're trying to imply is that the Linux kernel is not true open source any more today. Perhaps it is too big and h

      • I very much doubt your "eyeballs" theory. Who is good enough to do a competent job at it and willing to do it for free?
  • Laws in question (Score:5, Informative)

    by phantomfive ( 622387 ) on Wednesday October 23, 2024 @06:47PM (#64888889) Journal
    Here is what Linus had to say about which country made sanctions:

    I'm not a lawyer, so I'm not going to go into the details that I - and other maintainers - were told by lawyers. I'm also not going to start discussing legal issues with random internet people

    That's it. But he definitely made his opinion clear on the "Russian aggression."

    • by rta ( 559125 )

      The US doesn't currently look back with much pride on the Japanese Internment during WW2 (and German and Italian but nobody really talks about them much).

      From a security of the ecosystem POV this is relatively meaningless since the threat is not any higher than during normal times from either political or financial threats.

      From a "the EU is about to arrest me and i don't want to go to jail POV" it's ... understandable, but hardly something to be proud of. (And it's also "letting the terrorists win" kind

  • The root cause (Score:5, Insightful)

    by jovius ( 974690 ) on Wednesday October 23, 2024 @07:26PM (#64888957)

    Anyone disappointed by this should direct their indignation at Putin.

    It is telling that someone else is supposed to be blamed.

  • Brain drain (Score:5, Insightful)

    by Malay2bowman ( 10422660 ) on Wednesday October 23, 2024 @09:00PM (#64889131)
    As long as they are in Russia, physically, they are a liability. I know this sounds cold but think of the situation. You are Russian citizen, and you really hate Putin. You don't dare say it out loud but it's in your heart. You continue on as more or less as if he never existed. But then you get that knock on the door and you have orders to put back backdoors into the the software your global team is working on. At that point it's a wrap. You must comply, or face serious physical consequences which won't be as easy or merciful as a quick bullet in the head. Anyone physically in Russia can be conscripted to do these things at any time, and they won't even be able to warn the rest of the team. Putin's goons are watching and they better not do anything to raise suspicion in that team.
    • by Halo5 ( 63934 )

      Well put! This describes the situation perfectly IMO, and I think it's important to point these things out as it sounds as if Torvalds has already been thrust into the unfortunate situation of having to deal with state actors on these matters. It's bad enough having to stay vigilant against your ordinary, standard (peacetime?) bad actors, such as those related to the recent "XZ" incident. I expect that he has neither the time nor patience to deal with state-sponsored campaigns, so his response makes tota

    • by 1s44c ( 552956 )

      That reasoning is correct, but it probably applies to every other country too. Open source had always got around it by having lots of people checking and commenting on all code.

    • Re:Brain drain (Score:4, Insightful)

      by AmiMoJo ( 196126 ) on Thursday October 24, 2024 @04:19AM (#64889779) Homepage Journal

      If the Linux kernel team can't spot backdoors then there is a much bigger problem here, because it's likely that other governments are trying to sneak them in as well. Banning Russians because of fears over backdoors is no solution.

      There are good legal reasons to not accept patches from people inside Russia, but not good security reasons.

      • This is not about not accepting patches from Russia, this is only about removing Russians from the list of active maintainers.
      • If the Linux kernel team can't spot backdoors then there is a much bigger problem here, because it's likely that other governments are trying to sneak them in as well. Banning Russians because of fears over backdoors is no solution.

        Do you think that the fact that the backdoors might be detected in audits will stop the Russian government from coercing the attempt? IMO, the answer is clearly no, so the OP's point that the 'mere opportunity is a liability to the Russian developers' still stands.

        "Other governments" which contribute to the Linux kernel are less likely to use physical threats to force a developer to risk their reputation/career on a backdoor attempt.

      • As if a state actor couldn't make up a fake identity: make up a random name like "Jia Tan", start committing legitimate patches, and one or two years later, boom, you sneak in the payload.
  • What's missing here is someone mentioning which specific sanctions say you can't list names. I thought sanctions were about money transfers, not listing names of contributors who gave their work away for free.

    Did the work these contributors do get reverted too? Because it just sounds like their names were taken off it.

    • nothing at all like this happened, their names where only taken of the file that contains a list of people that you should contact in order to get your code merged.
  • You tell 'em Linus.

  • I am Russian. Does not matter where I live and what do I think, I was born Russian and that is impossible to change. Even considering that today's "views" allow "changing" anything, from the birthplace to skin color.

    I always considered OSS to be border-free and free from the politics. Russians, North Koreans, Cubans, Americans, Ukranians are all the same in OSS world as long as they do not bring their "real world" sh...t associations with them. They are judged by their contribution to the code, not by their

((lambda (foo) (bar foo)) (baz))

Working...