Puppy Linux Discussion Forum

Caught my eye

I read that article, well that's their fault. So they think that the buggy code will merge on the main kernel using flowering words? Open source devs are that kind of stupid. Most of them can read the code. The proposed code was reviewed first by the public then decide whether to merge it or not. Remember the PHP source code hacking incident when someone hack their git and try to add backdoor. But it caught by the prying eyes of open source community because the code was shown to the public. Deliberately putting a buggy code on open source code can show and prove to the public how lame the contributor is.

Linux kernel was commonly used by the industry. So experimenting with the mainline code and open source community is a very terrible idea.

What they did is borderline criminal.

I can't imagine the whole bunch of them aren't going to at least get fired over it.

This is why we can't have nice things ..

Torvald's weigh-in

Enjoy

Update on this saga

Last 5.4 kernel to definitely not have these 'patches' was 5.4.55 - hence Fossapup64-9.5 (5.4.53) should be fine. Of other branches, 5.5, 5.6, & 5.7 (up to 5.7.12) & earlier should be fine - hence ScPup64-20.06 (5.7.2) should also be fine. Kernels 5.9 through 5.12 - should wait for updates, as some serious security holes were apparently introduced by the UM staff & need to be manually worked through.

Its a very interesting journey.

The researchers attempted to "teach" a lesson but didn't get the reaction they expected.

What is exposed is that patches can, by accident or on-purpose, generate exploits. I think they were expecting a change in the acceptance process, but instead ...

I am sure, though, that this will have a bit of "a rethink" in practices going forward.

LARPing as the "red team" in real life is never a good idea.

The guy who thought he'd test airport security on his own after 9-11 ended up going to prison. These guys are going to at least have to look for a different line of work, because no one will hire them in IT after this.

Fixes for this will land in kernel 5.13. No news on backporting to earlier kernels.
https://www.phoronix.com/scan.php?page= ... -UMN-Fixes