← Back to context

Comment by jeroenhd

4 years ago

The concept of the research is quite good. The way this research was carried out, is downright unethical.

By submitting their bad code to the actual Linux mailing list, they have made Linux kernel developers part of their research without their knowledge or consent.

Some of this vandalism has made it down into the Linux kernel already. These researchers have sabotaged other people's software for their personal gain, another paper to boast about.

Had this been done with the developers' consent and with a way to pull out the patches before they actually hit the stable branches, then this could have been a valuable research. It's the way that the research was carried out that's the problem, and that's why everybody is hating on the researches (rather than the research matter itself).

To provide some parallel on how the research was carried about:

I see it as similar to

- allowing recording of people without their consent (or warrant),

- experimenting on PTSD by inducing PTSD without people consent,

- or medical experimentation without the subject consent.

And the arguments about not having anyone know:

Try to introduce yourself in the White House and when you get caught tell them "I was just testing your security procedures".

  • submitting a patch for review to test the strength of the review process is not equivalent to inducing PTSD in people without consent or breaking in to the Whitehouse. You're being ridiculous. Linux runs many of the worlds financial, medical, etc etc... institutions and they have exposed how easy it is to introduce a backdoor.

    If this was Facebook and not Linux everyone would look upon this very differently.

    • The fact that issues in Linux can kill people is exactly why they need leadership buy in first.

      There are ways to test social vulnerabilities (pentesting) and they all involve asking for permission first.