sko: From el reg: To us it seems whoever created the code would compromise or infect a selected Linux system and then install the backdoor on it. So if someone already gained privileges to install anything on one of your machines, it doesn't matter what it is - this host is compromised and has to be nuked from orbit.

So, unless I'm missing something this is not really about "the Linux kernel devs being compromised by NSA" as much as the endless list of Windows-targetting malware is not about "the NT kernel devs being compromised by NSA".

[–] [email protected] 1 points 1 day ago (1 children)

If this is the case, this still wouldn't exclude a NSA compromise though. There is the ban of Russian contributions.

You can say this is all about politics and the war, but then those politics are clearly aligned with US agencied interests. American contributions are still allowed despite the US being just as much as if not more of a threat to security and privacy. Just like they're just as war mongering.

[–] [email protected] 1 points 23 hours ago

I don't know the details of that part directly, but I do remember reading things like this which seemed to indicate delisting of some maintainers (positions of responsibility, as opposed to blocking all developer contributions) who were associated with certain sanctioned Russian companies. This seems to be in line with standard sanctions being imposed by many companies & organisations in various countries (not just USA). Regardless of personal opinions about whether that was "right, wrong, or otherwise" at the time it at least seems a far cry from "an NSA compromise".