13 ms·
Linux Foundation’s demands to the University of Minnesota
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- doener 6y ago"On the Feasibility of Stealthily Introducing Vulnerabilities in Open-Source Software via Hypocrite Commits": https://github.com/QiushiWu/QiushiWu.github.io/blob/main/papers/OpenSourceInsecurity.pdf https://github.com/QiushiWu/QiushiWu.github.io/blob/main/pap...
- stephenhuey 6y agoCan they prosecute UMN? A lot of people and businesses could have suffered extensive damages from their changes, and it seems like some kind of charge should hold up in court. Should we all contact UMN to complain? Edit: please explain why I’m being downvoted for asking sincere questions.
- hn8788 6y agoYou're probably being downvoted because "Should we all contact UMN to complain?" sounds like what twitter outrage mobs do.
- stephenhuey 6y agoFair enough, but I’m not advocating a DDOS attack or anything like that. Just a phone call or email similar to how we might contact our representative.
- dooglius 6y agoThis would effectively be a DDOS attack, whether or not you intend it as one.
- threatofrain 6y agoIf that’s the case, then although you can wish that all reps have huge staff to collect communications from their constituents, it’s not true, and telling people to call their reps would be even more DDOS because at least universities can act as a firewall. Your local reps in comparison will Never be as well resourced.
- dooglius 6y agoThe purpose of calling reps is to air grievances, everyone involved understands this, and they almost certainly have other phone lines for more critical functions. In contrast, a university is contacted for all sorts of reasons related to research/study, and complaining en mass would be highly disruptive to this.
- threatofrain 6y agoSo the argument you lead with is about extra phone lines? Then one can expect that professors have a university office line, and universities have Way More competency and discretionary budget in hiring PR firms and in-house staff to deal with dynamic and acute events. In terms of sheer muscle power, most public officials can't compare to the behemoth that is a university. They are even outclassed on agility. It may be your local official's job to do something, but the reality of budget anemia is stiffer than their obligations to you.
- zekrioca 6y agoThat's the problem with your suggestion. The authors of the papers did not mean to advocate to make human experiments either, yet they did. You suggestion would result in a DDoS attack anyway..
- syshum 6y agoMost likely because of the "suffered extensive damages", which does not seem to be supported by facts. This is more a pride / trust issue than it is actual damages
- invaliduser 6y agoHow is creating trust issues on a kernel not an actual damage?
- syshum 6y agoActual Damages is generally a legal term in which someone has to point to an actual dollar value of the damages they suffered. i.e John ran into my car, here is an estimate for $1,000 to repair the damages. Trust is very hard to make an actual damages claim for, it can be done but outside of the Linux Foundation I am not sure what companies would have an actual damages claim
- lmkg 6y agoActual Damages would be the time & effort to review previous patches for vulnerabilities, which is also the motivation for their demands from UMN. That's complicated by the fact that it's unpaid volunteer work, but a bill for the man-hours to evaluate the extent of the mess and clean it up seems like a clear-cut basis for establishing damages.
- HarryHirsch 6y agoHopefully, the Linux Foundation or someone with standing sends the university a bill - if they don't have intrinsic motivation to behave ethically, then the force of the market is a powerful motivation.
- dbcurtis 6y agoI have spent time doing contract development, and also made volunteer contributions to open source projects (not the Linux kernal, though). Certainly, if I were pulled into reviewing UMN kernel patches, I would be tracking my hours at my standard hourly rate, so that I would have the documentation for a claim for actual damages. Cleaning up other people's bad-faith crap is not what open source developers volunteer for. UMN caused real work for real people for bad-faith reasons, and should pay up. The work they caused is deflecting volunteers from otherwise productive activities. I suspect many volunteer kernel developers do contract development to pay the bills -- it should not be hard for them to just create a billing code for UMN clean-up. The Linux foundation can aggregate them all and dump that on UMN. (Also, I have a MSEE from UMN, and I can tell you that the next attempt at fund raising from me is not going to go well for them.)
- fluidcruft 6y agoWhat extensive damages could anyone have suffered from their actions? Anyone can knowingly or unknowingly submit "hypocrite" patches. Beyond that each of the patches fixed a different already-existing security flaw and the research design included removing the hypocrite feature with a followup patch and maintainer education if the first were accepted.
- bluGill 6y agoAs a graduate of the UMN these actions have reduced the value of my degree. Nobody should trust me because I'm probably tainted with the lack of ethics, and thus I'm unhireable. Fortunately I have a job that I'm proven in, but if they hit a downturn I might be in trouble.
- jefepstein 6y ago> As a graduate of the UMN these actions have reduced the value of my degree. Isn't that like saying an MIT Media Lab degree has reduced in value due to their relationship with Jeffrey Epstein, Nicky Negroponte and other deplorables.
- dvhh 6y agoAt least these "deplorables" weren't acting on behalf or with monetary contributions from the MIT Media Lab
- Accujack 6y ago>Isn't that like saying an MIT Media Lab degree has reduced in value due to their relationship with Jeffrey Epstein, Nicky Negroponte and other deplorables. Yes, and this is also true.
- bluGill 6y agoSortof, but I'll bet you heard of MIT in a good way before, while this is the only time you have heard of the UMN. Thus they are tainted different
- 6y ago
- weagle05 6y agoI'm giving you an upvote. Look around your house and count the number of linux kernels running. My count is 6 that I know about. I haven't seen the actual vulnerable code submitted to know how critical the vulnerabilities are but I believe these grad students are liable both civilly and criminally. Not advocating for mob justice but there needs to be more than a slap on the wrist. For those of us who live and breath software security everyday this is kind of a big deal.
- zekrioca 6y agoI don't agree this is the way to fix the bigger problem, which is the acceptance that every commit to the kernel is done in good faith. As mentioned in another comment, I believe having these grad students to take a look at the ethical impacts of their research is a way forward. Another would be to somehow cast some blame into their supervisor, which should know more. I understand that what they did was, and is bad and shouldn't be done. However how many other people do not also purposely submit buggy patches? In the end of the day, this happening just show vulnerabilities of the merging system itself.
- threatofrain 6y agoThe issue isn’t that every commit and committer is treated in good faith. They aren’t. The issue is that U of Minnesota, and universities in general, had a good standing reputation with the Linux kernel group. Students at the University can still submit patches, but not currently with the strength of institutional credibility standing behind them. Knowing who to trust and updating your trust when you’re wrong is part of healthy security.
- weagle05 6y agoI think we disagree on the bigger problem. In my view the bigger problem is the erosion of trust for open source. Over the last 10-ish years there has been a flood of research and marketing around open source software security. I wrote a white paper about it back in 2011. We know there are risks in open source and we know vulnerabilities are created both intentionally and accidentally. We also know open source maintainers are overworked and human. There will be mistakes and we must prepare for them. This is the reason why the fine folks at Sonatype, Snyk, and WhiteSource have jobs. These grad students wanted to make a splash and went after one of the most important code bases on the planet. It stopped being an ethical problem when the kernel maintainers had to manually search for vulnerabilities. They are using hours that could be used elsewhere. The Linux Foundation is paying Greg Kroah-Hartman to solve this problem, so they have a financial loss due to the actions of these grad students. There's your civil liability. They "knowingly cause(d) the transmission of a program, information, code, or command, and as a result of such conduct, intentionally causes damage without authorization, to a protected computer" so there's your criminal liability from the Computer Fraud and Abuse Act. There's probably criminal liability in the state where they live as well.
- tsujp 6y agoI'd argue yes. Linux is a dependency in a non-trivial subset of global infrastructure. If you tainted _without permission_ (implying no guidelines, no test scenario, no restrictions etc) your local water supply to see if you could and went with "It was a test! Here's some chlorine to fix it." you'd be in serious trouble. This study purposefully tainted the mainline kernel and in doing so absolutely everything that would be built on top of it. This was purposeful malicious action. Malicious actors should be punished.
- tw04 6y ago>Should we all contact UMN to complain? For what purpose other than to harass UMN staff? It's obvious they're well aware of the issue and that the community isn't happy with their actions. They've got staff and students that read HN and twitter. Calling them at this point doesn't accomplish much other than being a DDoS attack and shooting the messenger (there's no way you're going to get in contact with the people who actually conducted the study).
- Accujack 6y agoProsecute, no. However, if this were in a more traditional scientific field, this sort of error would be treated as a serious lapse of experimental oversight protocols and the school or the participants would be sanctioned according to their professional discipline (in this case, that would probably be the IEEE). Unethical experiments are a huge deal. If this had been an experiment on people face to face in e.g. a sociology context, then these students would likely have been expelled (and probably deported) and would likely be leaving the field. Since it was in an IT area, the U's oversight rules probably weren't even applied.
- underseacables 6y agoCan someone please explain in layman terms exactly what happened and why it’s a bad thing? I’m having a hard time figuring out why a pound of flesh needs to be extracted from the University.
- stephenhuey 6y agoThey were “researching” how feasible it is to submit insecure code. In other words, if can they slip some vulnerabilities past the maintainers. To me, it’s the same as sabotage. Not only is it unkind, but if it succeeded, many real people depending on that code could be negatively impacted.
- AnIdiotOnTheNet 6y agoThe real problem is that it wasn't done with the informed consent of any kernel maintainers. The information gathered during the exercise is potentially quite valuable for informing policy and procedure around how code is reviewed and accepted, it just wasn't gathered in an ethical way.
- voiper1 6y agoThere's a method for testing this sort of thing: pen-tests with consent from higher ups or "war games" with blue-team/red-team. It's not even a novel thing to do this properly.
- tmotwu 6y agoNope. Lets say IRB made the correct decision and demanded informed consent. Then informed consent must be requested from ALL participants, maintainers, and reviewers of the study. Higher up maintainers don't make that decision for others in this scenario, sorry. Novel or not, lets be completely honest with ourselves, it's not an easy experiment to frame properly.
- bakedbeanz 6y agoResearchers associated with UMN intentionally submitted patches to the Linux kernel with vulnerabilities in them as an experiment. OSS maintainers shouldn't have to be the unwitting test subjects of experiments and have their time wasted (or worse, have vulnerabilities make it into their source code) so that researchers can write a paper about it.
- pweissbrod 6y ago"Please provide to the public, in an expedited manner, all information necessary to identify all proposals of known-vulnerable code from any U of MN experiment. The information should include the name of each targeted software, the commit information, purported name of the proposer, email address, date/time, subject, and/or code, so that all software developers can quickly identify such proposals and potentially take remedial action for such experiments." That sounds more than reasonable as a request to make amends. The article said that finding all this code is a real problem. If UMN and the students involved are contrite that should be easy to fulfill.
- fluidcruft 6y agoI actually disagree as it would expose which maintainers accepted these sorts of patches and that can have implications for their reputations and livelihood. Beyond that, this is just "Open Source software can be vulnerable to bad actors (News at 10)".
- sokoloff 6y agoThat's true to a point, but hiding that information is arguably (and in my estimation) worse. "We better not look for other incidences of this nefarious behavior because it might create a small amount of collateral damage. Better to leave those patches unexamined."
- fluidcruft 6y agoUMN has already said they've opened an investigation?
- sokoloff 6y agoThere seems to be transparency value in having a different organization do the investigation than made the original judgment to approve the research. Maybe there's an "internal affairs" equivalent that we'd trust, but this reads to me like "UMN made an error in approving this research but don't worry because UMN is now going to look into it."
- fluidcruft 6y agoPeople who don't understand IRBs are vastly overstating the IRB issue. Yes, they should have sought it in advance, but on the other hand almost nobody in computer science gets human subjects research training. IRBs issue waivers of consent fairly often, particularly if there's extremely low risk to participants and disclosing the research will significantly affect the results (both of which are true here). This particular study would very likely have been granted an apriori waiver of consent without much hassle at all. Frankly, the study seems to have been fairly responsibly designed. They fixed actual kernel bugs, but included some additional more subtle latent bugs, if the subtle bugs were not detected, they corrected and removed the latent bugs and educated maintainers who accepted them.
- eCa 6y ago> IRBs issue waivers of consent fairly often, particularly if there's extremely low risk to participants and disclosing the research will significantly affect the results (both of which are true here). Apparently, the unwilling test subjects seems to strongly disagree with your conclusion in particular (I would guess) when it comes to the first point.
- fluidcruft 6y agoWell I'm sure this will become an IRB case-study, but I really don't think anyone is going to care.
- alpaca128 6y ago> there's extremely low risk to participants How do you plan to determine the potential risk for all kernel users in case the patch finds its way into a release? No IRB who understands this would ever approve of such "research". > disclosing the research will significantly affect the results Nothing a few 100% watertight patches as distraction and maybe cooperation from some maintainers couldn't fix to a reasonable degree. Either way that doesn't justify the experiment.
- fluidcruft 6y ago
- clarkevans 6y ago> The UMN has not said yet whether it will be withdrawn. Regardless of UMN's decision, perhaps the IEEE should consider withdraw of this paper from their journal regardless, their acceptance criteria reads: > Discuss steps taken to ensure that participants and others who might have been affected by an experiment were treated ethically and with respect. > If a paper raises significant ethical and/or legal concerns, it might be rejected based on these concerns. https://www.ieee-security.org/TC/SP2021/cfpapers.html#Ethical-Considerations-For-Human-Subject-Research https://www.ieee-security.org/TC/SP2021/cfpapers.html#Ethica... In their apology letter, the researchers seem to acknowledge they ran afoul of this requirement: > As many observers have pointed out to us, we made a mistake by not finding a way to consult with the community and obtain permission before running this study; we did that because we knew we could not ask the maintainers of Linux for permission...
- kdbg 6y agoThe paper was already withdrawn. https://www-users.cs.umn.edu/~kjlu/papers/withdrawal-letter.pdf https://www-users.cs.umn.edu/~kjlu/papers/withdrawal-letter....
- deleted 6y ago[deleted]
- dvhh 6y agoWhile I applaud the initiative (not that they need my recognition), I am somewhat afraid that such withdrawal would snuff out any further debate in the scientific community about proper ethical behavior and its delimitation ( which are admittedly fuzzy )
- tofof 6y ago> withdrawal would snuff out any further debate in the scientific community about proper ethical behavior You have this exactly backward. Far from "snuffing out" discussion of ethical behavior - the problem in the first place was that these researchers deliberately avoided the primary mechanism already in place to examine proper ethical behavior - their university's Institutional Review Board. The withdrawal is not an attempt to silence the discussion regarding the ethics at stake. Quite to the contrary, the withdrawal itself is an explicit admission of ethical failings: "our study design was inappropriate: specifically, it involved conducting research on the Linux kernel community without obtaining appropriate consent and approval." They continue, further conceding the ethical debate "We are withdrawing the paper so that we do not benefit from an improperly conducted study ... [and] to prevent our misguided research method from being seen as a model for how to conduct studies in the future." Nearly the entire issue at stake stems from the fact that these researchers did not properly use the Institutional Review Board already at their disposal. IRBs exist for the primary purpose of determining what proper ethical behavior IS, using existing widely-agreed-upon guidelines ("delimitation" in your terms) and judgment, and in ensuring such behaviors are followed. In particular, you normally must consult the IRB before any experiment is conducted on subjects. IRBs also serve as a primary party in the examination of any allegations of ethical misconduct. The researchers in question only consulted their IRB after already conducting the research and publishing its abstract to twitter, for which they received "heated discussion and pushback," and were then forced to removed the abstract and apologize to their own IRB for causing "many confusions and misunderstandings" according to the linked article.
- hackeraccount 6y agoIRB - Institutional Review Board see https://slatestarcodex.com/2017/08/29/my-irb-nightmare/ https://slatestarcodex.com/2017/08/29/my-irb-nightmare/
- fartcannon 6y agoIf I were an organization with intent on profiting from a space where a competitor offered a free equivalent or better product, that had a religious like following that was rapidly gaining support, what could I do? First, I could undermine the de facto leaders of those spaces with topical period appropriate accusations which, at the very least, limits their social power and thus their power to defend themselves and their groups. Second, I can undermine the public's trust in what they offer. Sure, call me paranoid. But this wouldn't be the first time this has happened.
- rognjen 6y agoI understand your point as a thought experiment rather then a conspiracy theory in earnest so I don't think your down votes are justified. However, I disagree with your second point. The way this is being handled has only increased my trust in the Linux Foundation.
- fartcannon 6y agoIt is nice, isn't it. I find their work inspirational.
- kdbg 6y agoSo kinda a quick summary given the available information that I've seen. Back in August 2020 some research was performed looking at introducing vulnerabilities into the Linux Kernel.[0] The paper indicates that three patches were submitted via anonymous gmail accounts to the mailing list and were never committed. The reviewers were provided a proper patch upon accepting the vulnerable one and received explicit confirmation that the maintainers would not move forward with the vulnerable patch. I'm not sure when exactly questions started being raised about that research. Though I first became aware of it in December. The discussion was mostly around the human involvement and led to the prepublication of the paper being removed and clarifications being issued.[1] Fast-forward to April 2021. The patch seems to have kicked things off[2]. This was called out as being an impossible situation, and as being a "known-invalid patch" by Greg KH [3]. It appears that at least three patches by this same author introduced vulnerabilities[4] according to Leon Romanovsky. Though I don't have links to the specific patches. Leading to U.Mn's ban from contributing to the kernel by Greg KH[5] --------- What is in my opinion unclear at least to me is whether these more recent patches are actually in bad faith or just simply bad. The prevailing theory is that they are part of more research into introducing vulnerabilities. As already stated though, that research and its paper were done in August of 2020. The more recent commits, the official story from Kangjie Lu, Qiushi Wu, and Aditya Pakki[6] are that they are part of "a new project that aims to automatically identify bugs introduced by other patches". This does somewhat align with statements[7] made indicating that the commits were from a static analysis tool being researched which was made prior to this blowing up. Though I will note that the author of that patch was _not_ one of the authors of the apology letter, so may genuinely be unrelated. This tool story was not believed by Greg KH[8]. And his take is the one that has gained a lot of adoption. That these patches were intentionally made in bad faith for another paper. I will state that the newer patches that caused problems did _not_ follow the methodology that the original research followed to try to prevent vulnerabilities from actually being introduced into the repo. The original paper, while certainly had issues with methodology and experimenting on people inappropriately, did take steps to prevent any actual vulnerabilities from being committed, whereas the ones in question did not, and even made it to stable branches. If the official story from U.Mn is true the commits should also have been noted as having been found by a tool, and followed the proper procedure for that, which they did not do. Though it does appear that the vast majority of the patches that were reverted were legitimate patches.[9] Atleast spot checking replies on that mailing list. I mean on a whole the original research was questionable, but I kind of want to be more charitable in my interpretation of the more recent events but honestly that original patch that kicked things off is pretty bad. [0] https://github.com/QiushiWu/QiushiWu.github.io/blob/main/papers/OpenSourceInsecurity.pdf https://github.com/QiushiWu/QiushiWu.github.io/blob/main/pap... [1] https://www-users.cs.umn.edu/~kjlu/papers/clarifications-hc.pdf https://www-users.cs.umn.edu/~kjlu/papers/clarifications-hc.... [2] https://lore.kernel.org/linux-nfs/20210407001658.2208535-1-pakki001@umn.edu/ https://lore.kernel.org/linux-nfs/20210407001658.2208535-1-p... [3] https://lore.kernel.org/linux-nfs/YH5%2Fi7OvsjSmqADv@kroah.com/ https://lore.kernel.org/linux-nfs/YH5%2Fi7OvsjSmqADv@kroah.c... [4] https://lore.kernel.org/linux-nfs/YH+zwQgBBGUJdiVK@unreal/ https://lore.kernel.org/linux-nfs/YH+zwQgBBGUJdiVK@unreal/ [5] https://lore.kernel.org/linux-nfs/YH+7ZydHv4+Y1hlx@kroah.com/ https://lore.kernel.org/linux-nfs/YH+7ZydHv4+Y1hlx@kroah.com... [6] https://lore.kernel.org/lkml/CAK8KejpUVLxmqp026JY7x5GzHU2YJLPU8SzTZUNXU2OXC70ZQQ@mail.gmail.com/#r https://lore.kernel.org/lkml/CAK8KejpUVLxmqp026JY7x5GzHU2YJL... [7] https://lore.kernel.org/lkml/CAAa=b7dnrz5Pz5hMUc29VHJb9ucFkWArd2sbsCUO+POfuFXFhA@mail.gmail.com/ https://lore.kernel.org/lkml/CAAa=b7dnrz5Pz5hMUc29VHJb9ucFkW... [8] https://lore.kernel.org/lkml/YH%2FfM%2FTsbmcZzwnX@kroah.com/ https://lore.kernel.org/lkml/YH%2FfM%2FTsbmcZzwnX@kroah.com/ [9] https://lore.kernel.org/lkml/202104221451.292A6ED4@keescook/ https://lore.kernel.org/lkml/202104221451.292A6ED4@keescook/
- protomyth 6y agoIs there a link to the actual letter of demand?
- asciimov 6y agoIf anything, this whole case underscores the fact that Engineering and Computer Science schools/colleges need to be teaching ethics as a core part of their curriculum. It is appalling to my partner, a phd in bio research, that even as undergrads we didn't have at least a couple of courses covering what ethics was, how it informs, and how it applies to everything we do. Worst of all, because of this lack of education, many big tech firms have done unethical experimentation on us unsuspecting users, simply because the developers never questioned if they should do it.
- _wldu 6y agoI agree. I've also noticed that some developers seem to have a strong sense of "we should not do that" while others don't and I'm not sure why. One recent example was impersonating/spoofing a manager's email to send phishing emails as part of a security compliance test. One developer saw no harm at all in doing so while another felt we should ask permission first. It's a basic violation of trust to do this sort of thing and in the very least, permission should be obtained first. Otherwise, the violation of trust and repercussions may be severe.
- bmhin 6y agoAs someone who naturally gets feelings of aversion when I hear some solutions suggested and who works with folks who can suggest them without blinking, I honestly think "should" never enters their mind. It seems to be a pure engineering-in-a-vacuum mindset where "can" is all that matters. They envision an admittedly potentially interesting end outcome and the means to get there is just engineering. They don't think twice about how their solution just involved enabling tracking everyone's phone's location to enable it. My and many others first thought would likely be "I don't really want to be tracked myself or have to track others" and all they think of is "We can dynamically allocate the resources based on where people are!".
- silicon2401 6y agoI disagree. I went to school to learn how to solve problems, not somebody's subjective view of ethics. Let people who care about ethics take ethics courses if they really want to. Make corporations responsible for behaving ethically and then figure out how they want to handle it. As a private person, I live life by my own ethics and am not interested in spending my money to have somebody else lecture me on their ethics.
- maweki 6y ago"researchers appear to have been experimenting on people," Nice of the Kernel community to spell this out in no uncertain terms. The original apology did not acknowledge this fact.
- zero_deg_kevin 6y agoMaybe we’ll see a UMN clause added to popular open source licenses to combat this sort of behavior. Maybe it’ll be “don’t do this” or it’ll go as far as “don’t do this or your right to legally use this software is terminated immediately.”
- orwell2012 6y agoA little remimder for all the people advocating for teaching "Ethics" to students/researchers: Linux Foundation is sponsored by Microsoft, Google, Intel etc. Need a mirror to look at, anybody?
- deleted 6y ago[deleted]
- vimax 6y ago"But when you're charged with maintaining the most important operating system on the planet" Correction, two planets.