Code

Why the Linux Team Banned the University of Minnesota

Why the Linux Team Banned the University of Minnesota

Free Python Course ➞ Mini-course for beginners and experienced coders. 4 cool projects in the portfolio, live communication with the speaker. Click and discover what you can learn in the course.

Learn More

On April 21, 2021, Greg Kroah-Hartman, a key Linux kernel developer, announced the blocking of all commits from the University of Minnesota. This decision was the result of significant analysis and several incidents involving code contributed by university researchers. In this context, it is important to understand how this situation occurred and what implications it may have for the Linux kernel development community. The development team's position emphasizes the need to maintain high standards of quality and security for code contributed to the project. Commit locking has become an important step in ensuring the integrity and reliability of the Linux kernel, and raises questions about the interaction between academia and open source software.

What happened

In 2020, Kangjie Lu, an associate professor in the Department of Computer Science and Engineering at the University of Minnesota, and Qiushi Wu, a graduate student at American College, presented a paper investigating the stealthy introduction of vulnerabilities into open source software through the use of fake commits. This research highlights the importance of security in open source projects and focuses on the potential risks associated with repository manipulation. Given the growing popularity of open source software, understanding such threats is becoming critical for developers and users.

The authors described their attempts to introduce several vulnerabilities into the Linux kernel. They submitted several commits that appeared to be fixes for real bugs. Liu and Wu stated that this was merely a research project aimed at identifying problems in the open-source software development process. They emphasized that no one on the Linux kernel team was aware of their intentions.

The researchers note that the vulnerabilities were not included in the final version of the Linux code. All false patches were identified and rejected by the community during the commit discussion stage. However, Kroah-Hartman claims that one of the patches did end up in the repositories, but did not cause any harm.

We presented the results of our research to the community before the official publication of the article and collected the participants' feedback. These comments are included in our article.

Liu and Wu: Explanatory Note

This explanatory note is devoted to the concept of Liu and Wu, which considers important aspects of interaction and harmony in various spheres of life. This concept emphasizes the importance of balance and understanding, which is especially relevant in the modern world.

The concepts of Liu and Wu represent two sides of the same coin, reflecting the dynamics of relationships between people, as well as nature and the environment. Liu symbolizes gentleness, flexibility, and adaptability, while Wu embodies strength, tenacity, and resilience. Their interaction creates conditions for harmonious coexistence and effective cooperation.

The importance of understanding these concepts is evident in various fields, such as psychology, sociology, and ecology. Effective application of Liu and Wu's principles can contribute to improved communication, conflict resolution, and the creation of sustainable relationships on both a personal and social level.

In conclusion, considering Liu and Wu's concepts not only enriches our understanding of human relationships but also opens new horizons for building a harmonious and sustainable society.

This article was written in the context of a significant event in the field of cybersecurity. Shortly before its publication, hackers carried out one of the most high-profile attacks in recent years, targeting SolarWinds' Orion software. By injecting malicious code, the attack affected the computers of numerous company clients. This incident is a clear example of a supply chain attack, highlighting the importance of protecting not only end users but also supplier infrastructure.

Researchers from the University of Minnesota may have sought to draw attention to their work and conduct an experiment on the developers of the Linux kernel, one of the most prominent open source projects.

Linux kernel developers prefer to focus on mission-critical tasks rather than participating in experiments. Their primary goal is to ensure the stability and security of the system, which requires significant effort and resources. Therefore, any attempts to implement non-standard solutions can distract from important work and negatively affect the quality of the final product.

Greg Kroah-Hartman is a personal Twitter account where he shares his thoughts and ideas. Greg's page features relevant discussions, analytical commentary, and unique perspectives on various events. The importance of his account is that it provides subscribers with the opportunity to follow the latest news and trends, as well as participate in open discussions. By subscribing to Greg Kroah-Hartman, you gain access to engaging content that can broaden your horizons and deepen your understanding of current topics.

Linux Community Reaction

The Linux community has reacted strongly to a recent paper in which researchers conducted experiments with the Linux kernel. The main complaint is that the team failed to notify the community of their actions, which calls into question the ethics of their approach. In fact, their actions can be compared to a hacker attack, as they violated generally accepted standards for external security testing (Red Team security testing), which require the attacked party to be aware of the tests being conducted. Researchers from the University of Minnesota ignored these rules and acted at their own risk, sparking a storm of discontent among members of the Linux community. Wu and Liu, in fact, targeted not only the development community but also the fundamental philosophy of Linux. Linux users tend to trust kernel developers, which is an important aspect of the operating system ecosystem. This situation raises questions about trust, transparency, and security in open source software, which is becoming increasingly relevant in today's technological world. Open source, by its very nature, relies on an active community. Developers are needed to write, document, and use code, as well as provide feedback, allowing for continuous improvement of the software. Therefore, the successful functioning of open source projects relies on the efforts of many people, and this requires a certain level of trust in the development system. When this trust is undermined, it negatively impacts the entire ecosystem.

Greg Scott, a 20-year veteran of open source development, shared his opinion in a commentary for Gamers Grade. His professional experience and deep understanding of technology make him valuable to the developer and gaming communities. Scott emphasizes the importance of open source software in the modern world and its impact on the development of the gaming industry.

Jared Floyd of Red Hat was even more categorical in comments for Zdnet.

This is like saying you're doing security research when in reality you're heading to a supermarket parking lot to disable the brakes of every car in the lot. The goal is to see how many people will be in an accident. This approach is not only unethical but also dangerous, as it has real-world consequences for people and property. Security research should be based on ethical and safe practices aimed at preventing incidents, not creating them.

Developers have also expressed dissatisfaction with the time and resources spent on testing experimental patches. This is frustrating for both volunteers who work on the Linux project in their spare time and for companies that fund open source development or employ programmers to work on the Linux kernel full-time. This inefficient use of time can negatively impact the project's progress and reduce the motivation of contributors.

Following the publication of the article, many Linux kernel developers concluded that the patches provided by the University of Minnesota needed to be reviewed. However, these patches never received a full review. This raises important questions about the quality and reliability of kernel changes and how the community can more effectively handle similar situations in the future.

Continued

On April 6, 2021, graduate student Aditya Pakki submitted a patch to the Linux kernel from his university email address. At first glance, the patch seemed innocuous and was intended to improve the code quality, which initially led to its approval. However, on April 9, one community member, Eric Dumaze, expressed doubts about the quality of the patch.

On April 19, Linux community veteran Al Viro criticized his colleagues for approving a patch that he believed did not introduce real fixes. The discussion became more tense after it was revealed that the commit was submitted from a University of Minnesota domain. This raised important questions about the quality and appropriateness of the code changes, which in turn could impact the stability and security of the project.

The next day, April 20th, Greg Kroah-Hartman intervened. He sent Packey a letter asking him to stop submitting ineffective patches. In his message, he expressed dissatisfaction, claiming that their professor was using inappropriate methods to publish a new paper.

Community members analyzed Packey's four previous patches and identified vulnerabilities in three of them.

The story could have ended there, but Packey unexpectedly responded to Kroah-Hartman: "I ask you to stop making baseless accusations that could be considered slander." The graduate student claimed that a new static code analyzer of his own creation was used to develop these patches.

On April 21st, Kroah-Hartman refuted Packie's claim, noting that the patches were developed without a static code analyzer and do not actually introduce any fixes.

Your team has openly admitted to submitting knowingly harmful patches to gauge community reaction. You even published an article documenting these events. Now you are again submitting clearly incorrect patches. How should I respond to this situation?

The kernel.org discussion thread provides important insights into Linux kernel development. Participants discuss a variety of technical issues, including performance optimization, bug fixes, and new feature implementations. Discussions on this forum are a valuable source of information for developers, providing insight into current development trends and potential changes for future kernel versions. Active community participation in these discussions contributes to improved code quality and increased system security. Thus, the kernel.org correspondence plays a key role in the development and support of the Linux project, ensuring the exchange of knowledge and experience among developers.

That same day, Greg officially announced that commits coming from the umn.edu address would be rejected by the community. To back up his words, he rejected 190 submissions from users associated with the university. This decision underscores the importance of code quality and adherence to standards in the project, as well as the need for strict control over the sources of changes.

On April 23, Linus Torvalds expressed his position, stating that the researchers' actions had undermined trust in the community, and therefore the suspension of the university was justified. That same day, Mike Dolan, Senior Vice President of the Linux Foundation, sent a letter to the university with four key demands. These demands are aimed at restoring trust and improving communication between researchers and the development community.

Provide the information necessary to identify all malicious patches submitted during Liu's experiment. This will allow for an in-depth analysis and assessment of the potential threats associated with the use of these patches. It is important to thoroughly investigate their impact on systems and data security in order to develop effective protection strategies.

Retracting an article means removing it from public access on a website or platform. This may be necessary for a variety of reasons, such as outdated information, the need for edits, or changes in editorial policy. The process of retracting an article typically involves removing the link to it and blocking access to users. This helps maintain the relevance of the content and improve the quality of information presented to readers.

It is important to ensure that future experiments by university staff are conducted in accordance with established standards and norms in the scientific community. This will help maintain high ethical and professional standards in scientific activity.

Consent from all participants must be obtained before the experiment begins. This not only complies with ethical standards but also ensures that participants understand their rights and responsibilities. Consent must be informed, meaning that participants should be given full information about the goals, methods, and potential risks of the experiment. This will ensure transparency and increase trust between researchers and participants.

Liu and Wu have successfully completed two key steps: they retracted their paper and provided full disclosure of their research. They and Packy have issued an apology to the Linux community, underscoring their responsibility and commitment to scientific integrity.

The need to demonstrate this type of "attack" is long overdue. This paper has generated significant discussion, and I believe the researchers deserve recognition for their work.

Christoph Hellwig, a well-known Linux kernel developer, actively participates in discussions on the kernel.org platform. His contributions to the Linux kernel are significant to the community of developers and users of the operating system. On kernel.org, Hellwig shares his knowledge and experience and participates in discussions of new features and improvements that affect the performance and stability of the kernel. These discussions help shape the future of Linux and make it more adaptive to modern user requirements.