Overly broad permissions can turn one compromised account into a much larger security problem. Learn how to reduce unnecessary access, review privileges, and apply least privilege across modern Linux systems. Review Linux Privileges×
Desktop Security
security advisory vulnerability
security advisory vulnerability GNOME is officially shortening its standard vulnerability disclosure window from 90 days to 30 days, a change that impacts upstream maintainers, downstream Linux distributions, and system administrators in how they handle software vulnerabilities. The policy shift, announced by long-time security coordinator Michael Catanzaro , addresses modern software patching realities and a growing influx of automated submissions. . Because GNOME is the default desktop environment on several major Linux...
Jul 21, 2026
Security Vulnerabilities security advisory moderate
security advisory moderate For organizations that run a self-hosted Git platform, it’s no longer just about hosting static code repositories. Today, Git servers are responsible for deployment pipelines, API tokens, SSH keys, package repositories, and the automation scripts that push code directly. Confirm that the upgrade addresses known vulnerabilities but also provides production environments. . That makes them trusted systems within the development environment and attractive targets for attackers looking to move...
Jul 20, 2026
Server Securitydata privacy automation
data privacy automation Every system admin has lived through the same Monday morning ritual. A queue of forty tickets, half of them password resets, permission errors, or disk space warnings that any experienced technician could resolve in under two minutes. The other half require actual judgment. For years, automation promised that software would eventually sort the two apart on its own. That promise is now being tested in production Linux environments. . Early results are reshaping how IT teams think about tier-1...
Jul 17, 2026
Privacydata collection automation
data collection automation You're running a web scraping project to collect pricing data from e-commerce sites. You set up a pool of datacenter proxies, launch your scripts, and within minutes — banned . CAPTCHAs everywhere. Your data pipeline stops before it really begins. . It's a frustrating scenario that plays out daily in ad verification, market research, and multi-account management. The website doesn't know you're doing legitimate research or monitoring. It just sees traffic coming from IP ranges it recognizes as...
Jul 17, 2026
Security Trends security advisory social engineering
security advisory social engineering Business Email Compromise used to be a numbers game — mass-blasted emails, broken English, an obvious "URGENT WIRE TRANSFER" subject line. That era is over. Generative AI has turned BEC into a tailored, low-noise operation that mimics writing style, voice, and even video presence. This piece looks at what's actually changed under the hood, what defenders are testing in response, and why so many organizations are still structurally unprepared for it. . The Infrastructure Problem Nobody Wants to...
Jul 17, 2026
Refine news
X Clear Filters
Get the latest News and Insights
Get the latest Linux and open source security news straight to your inbox.
Community Poll
Should Linux servers automatically install security updates?
Trending News
Loading...
Explore Latest Linux Security news
We found 12 articles for you...
209
security advisorypatch managementcommunity engagementNavigating Open Source Security with TuxCare Insights and Strategies
We Linux security admins are always searching for the latest insights to help us secure our systems against current and emerging threats. A recent TuxCare report on open-source security risks and trends shares some crucial insights that open-source community members and Linux security admins should be aware of. . As many organizations move away from CentOS 7 and choose new Linux distributions, our security strategies must stay ahead of the curve. Staying on top of your patch management and vulnerability assessments is more critical than ever to fend off emerging threats. And let's not forget the open-source supply chain – it's a fantastic resource and a potential weak spot if vulnerabilities like the XZ backdoor aren't caught in time! The buzz around AI in enterprise strategies is real, and while it offers exciting possibilities, it does require a careful approach. We must implement AI tools that enhance security while being wary of potential risks. It is crucial to keep our skills sharp with regular training and connect with the wider open-source community. To help you adopt these practical measures and stay informed of the latest trends, let's examine the key findings and takeaways of this recent report and discuss practices you can engage in to overcome these security challenges. Transitioning from CentOS 7: A Paradigm Shift With discontinued support for CentOS 7 , organizations are migrating away from it in favor of other enterprise Linux distributions, forcing security administrators to adjust their strategies. This task involves more than simply switching distributions—it also involves ensuring security protocols, configurations, and monitoring tools fit seamlessly within your new environment. TuxCare's recent report shows that more and more enterprises are turning towards distributions such as Ubuntu, Debian, and Red Hat variants to meet their operational requirements. As they transition, it is essential to review current security measures. In particular, administratorsmust ensure their chosen distribution supports existing security tools and is compatible with enterprise-wide policies. Simply put, maintaining similar or higher security and integrity levels during and post-transition requires careful planning and proactive management. The Importance of Proactive Patch Management Patch management is an indispensable component of security administration, serving as an essential defense mechanism against vulnerabilities and exploits. As demonstrated in TuxCare's report, timely patch implementation could have avoided numerous breaches, yet many organizations delay patching due to concerns about system downtime or operational disruptions. Security admins should consider automated patch management solutions to address this common concern. Updates should be applied during off-peak hours or gradually to limit disruptions. Continuous compliance monitoring must also be conducted to keep systems protected against new threats. Regular audits of defense mechanisms will ensure these requirements remain current and complete. Strengthening the Open-Source Supply Chain Open Source provides access to an incredible wealth of tools and resources; however, its security risks must not be overlooked. As illustrated by TuxCare's report on the case of the notorious XZ backdoor incident, open-source components sourced from third parties present potential security threats . Hence, meticulous checks must be conducted before adding them to your environment. Audits of vendors and code should form part of your ongoing security strategy. Tools like Software Composition Analysis (SCA) provide visibility into dependencies and licenses of third-party code to detect vulnerabilities quickly and remediate them promptly. Community engagement also plays an integral part in strengthening supply chain security. Actively participating in open source communities provides early insights into emerging threats and patches, speeding up reactions when possible vulnerabilitiesemerge. Harnessing AI Cautiously AI is making waves across nearly every industry, and security, in particular, has seen great benefit . According to the recent TuxCare report, however, while AI can effectively boost security measures, it should only be adopted cautiously. Some AI tools help identify patterns or anomalies missed by traditional methods and enhance incident detection and response capabilities. However, AI systems may become targets, raising risks of adversarial attacks through malicious entities feeding them falsified data to disrupt operations or bypass security measures. Therefore, a layered approach that includes AI solutions should complement rather than replace proven practices. Regular updates and audits of AI models are necessary to secure them against emerging threats, and security teams should receive training on using AI technologies effectively and safely. We admins can use AI to further our security efforts by taking this route and effectively managing associated risks. Continuous Learning and Community Engagement Staying ahead in cybersecurity requires constant learning and adaptation. Continuous education for security teams to stay abreast of threats, vulnerabilities, technologies, and best practices is crucial. Many organizations offer in-depth cybersecurity training programs that cover tools, techniques, and best practices. Engaging the community is also vital. Subscribing to open-source security newsletters and participating in open-source projects, forums, and industry conferences is invaluable for gathering valuable insight and fostering peer collaboration. TuxCare highlights this strength by emphasizing community-driven security, where sharing knowledge and resources strengthens collective resilience against threats. Our Final Thoughts on These Open Source Security Trends & Challenges Navigating the ever-evolving challenges we Linux security admins face demands an adaptive and comprehensive strategy, according to TuxCare's report. Keystrategies involve adapting to new distributions, improving patch management practices, protecting open-source supply chains from attack, and safely integrating AI into your environment. At the same time, staying informed, continuously learning, engaging with open source communities, and anticipating emerging threats is crucial for adaptive and resilient protection. How are you navigating these open source security challenges? Share your tips @lnxsec! . As open-source security advances, proactive trends emerge: prioritizing patch management, integrating AI for threat detection, and fostering community collaboration to bolster defenses. patch management strategies, cybersecurity AI tools, open-source risks, community-based security efforts. . Brittany Day
Apr 15, 2025
•
Security Trends
76
risk managementsecurity practicessecurity measuresOpenSSF: Security Baseline Initiative Enhances Open-Source Protection
Open Source Security Foundation (OpenSSF) recently unveiled its Security Baseline initiative to assist Linux security admins and developers in incorporating essential security measures into open-source projects. This set of guidelines, available on February 25, offers three tiers of practices explicitly tailored for project maturity levels, ensuring open-source software provides consistent and dependable protection from day one. . Understanding and following these guidelines means taking proactive measures against vulnerabilities while strengthening user trust in projects. Operating at version 20250225, the OSPS Baseline outlines basic security for open-source projects, serving as a practical guide for developers and project maintainers. This initiative encourages security awareness within communities so everyone can collaborate to refine and improve practices. Adding this guideline into your workflow can make the open-source ecosystem safer while aligning yourself with broader community efforts to remain vigilant against security threats. Let's take a closer look at this initiative, its significance, and practical measures you can take to adhere to these guidelines while overcoming implementation challenges. Understanding the Security Baseline Initiative On February 25, OpenSSF introduced its Security Baseline initiative, providing an organized framework for securing open-source projects according to their level of maturity. Since open-source software development involves collaborative efforts without central oversight, maintaining consistent standards can be challenging. Thankfully, the Security Baseline offers three guidelines that ensure basic security fundamentals are always met. This design makes this initiative particularly advantageous for diverse projects ranging from fledgling developments to mature software offerings. Why Tiered Guidelines Matter Security in software development cannot be addressed with one-size-fits-all solutions. Projects vary significantly incomplexity, size, and sensitivity - therefore, security frameworks and solutions must reflect this diversity. The Security Baseline's tiered guidelines were specifically tailored to this reality to enable projects at various stages of maturity to adopt appropriate security practices at different points during their journeys. This scalability ensures burgeoning projects start with manageable security goals while adding more sophisticated measures as they expand. As a result, it supports projects as they develop, facilitating sustained security improvement over their lifecycles. Building Trust in Open-Source Software One of the main objectives of the Security Baseline is to build trust in open-source software by assuring its security is comparable with proprietary solutions. Security breaches and vulnerabilities can erode trust in an open-source project and prompt users to seek alternatives. By adhering to OpenSSF guidelines, developers can demonstrate their dedication to user and stakeholder security and position projects favorably in trust-driven ecosystems. Engaging the Linux Security Community in This Initiative Linux security admins will play an instrumental role in adopting and implementing the OpenSSF Security Baseline. As security leaders within their projects, these individuals are in an ideal position to advocate for and integrate this set of guidelines into existing workflows, thus leading initiatives prioritizing security from their inception and creating an atmosphere that values proactive risk management practices. The Security Baseline allows Linux admins to interact with and engage with the broader security community. With its active maintenance and open-source nature, there is room for collaboration and contribution - and community members are encouraged to provide feedback, suggest improvements, and refine the guidelines in response to emerging security threats or advancements in technology. A Practical Guide to Implementation Implementing the Security Baseline within aproject begins with understanding the project's security needs and maturity level. This includes a current security posture assessment, gap analysis, and selecting appropriate tier levels from guidelines to address those gaps. Newer projects might focus on security measures like secure coding practices or vulnerability scanning . In contrast, more mature ones could focus more heavily on advanced threat modeling and incident response plans. Open-source initiatives provide greater flexibility when applying these guidelines, enabling administrative teams to tailor practices according to their operational environment. By carefully considering each tier, projects can create an adaptive security strategy that scales with their growth while responding quickly to changing risks. Overcoming Common Challenges Adopting new security guidelines can be challenging for projects with limited resources or stretched teams. One key solution lies in education and awareness: ensuring all contributors understand why security is necessary and how it can be incorporated into their work without disrupting the workflow. Collaboration is another vital asset. Networking with other projects and developers who have successfully applied the guidelines can provide invaluable practical insight and experiences to guide your efforts. This community-centric approach to open-source development fosters increased collective security through shared knowledge. Our Final Thoughts: Understanding The Path Forward As the open-source community expands, its security challenges will also grow. To meet this need, the OpenSSF Security Baseline initiative was formed. By adopting its guidelines, we Linux security admins and developers can increase our projects' security while protecting ourselves from emerging threats and building trust between ourselves and users. The journey towards comprehensive open-source security is complex yet rewarding. Initiatives like Security Baseline are helping the open-source community meet challengeshead-on while making sure open-source software remains an enduring platform for innovation now and in the future. Have you adopted the OpenSSF Security Baseline guidelines in your open-source development workflow? Let us know on X @lnxsec ! . Bolster the resilience of open-source applications by implementing multi-level protocols from the OpenSSF framework, aimed at reducing vulnerabilities and fostering confidence.. OpenSSF, security practices, open-source guidelines, risk management, Linux admin. . Brittany Day
Feb 27, 2025
•
Organizations/Events
76
browser securitysecurity strategycommunity engagementLinux Foundation: Transforming Chromium Development for Enhanced Security
As Linux security admins, staying ahead of the curve is paramount, especially regarding the browsers you use and manage. On January 9, 2025, The Linux Foundation is unveiling "Supporters of Chromium-Based Browsers," an initiative supported by tech titans including Google, Meta, Microsoft, and Opera. This project is expected to transform the open development ecosystem surrounding Chromium (the foundation behind popular browsers such as Google Chrome and Microsoft Edge) through an open governance model and industry collaboration that promises greater transparency, security, and customization for Chromium-based browsers while aligning perfectly with open-source community's security needs. . This is a golden opportunity for us Linux security admins to engage with a community-driven project prioritizing security and innovation. We’ll have more control over updates and browser features, minimizing unnecessary integrations and tightening security measures where it counts. The collaborative nature of the initiative ensures continuous scrutiny and improvement of security features, fostering an environment where potential vulnerabilities are swiftly addressed. With its open-source approach, you can trust that compliance and security standards are met with thorough community verification. Let's examine this initiative in more depth and explore how it will enhance your browser security strategies, keeping your systems safe and efficient. Strengthening Open Development One of the most exciting aspects of the "Supporters of Chromium-Based Browsers" initiative is its dedication to open development. By providing a neutral space where developers and the open-source community can come together, this initiative seeks to support existing Chromium projects and any that emerge - encouraging innovation while freeing various stakeholders from restrictions associated with proprietary solutions. We can expect a steady flow of features and updates developed collaboratively by the community to addressusers' needs and concerns. Open development also means increased transparency. Since the code and development processes are open, it's easier to understand the security measures being implemented. This transparency builds trust and allows for better-informed decision-making when configuring and deploying these browsers in your environment. Governance and Industry Support A key distinguishing feature of this initiative is its open governance model, with a technical advisory committee overseeing development to ensure it meets community needs rather than solely serving single entities' interests. This governance model seeks to promote balanced decision-making processes where voices from various sectors - security experts, developers, and end-users can all have their say and be considered in decision-making processes. Major tech companies such as Google, Meta, Microsoft, and Opera provide financial backing and invaluable expertise and resources. These companies are committing to funding and development, which means that the project will have the resources needed to tackle significant challenges, including those related to security. This industry support translates to a more robust and reliable browser that benefits from the combined experience and resources of some of the biggest names in tech. Impact on Chromium vs. Chrome Understanding the differences between Chromium and Google Chrome is vital to fully grasp the impact this initiative will have on users. Although Chromium serves as the basis of Chrome, certain features and integrations specific to Google services (like Chrome Sync) or licensed codecs for H.264 and AAC are missing from it. It also excludes DRM modules such as Google’s Widevine. Though these differences seem like limitations, they present an opportunity from a security perspective. By avoiding deep integration with Google services, Chromium has a smaller attack surface, reducing potential vectors for exploitation. This is particularly beneficial for environments whereminimalism and security are paramount. Linux security admins can configure Chromium-based browsers to fit their specific security needs without the additional bloat and potential vulnerabilities associated with proprietary features. Security Through Community Collaboration One of the most significant advantages of the "Supporters of Chromium-Based Browsers" initiative is the potential for enhanced security through community collaboration. With more developers and organizations contributing to the project, there will be increased scrutiny of the code . This collaborative effort ensures that security vulnerabilities are identified and resolved quickly, benefiting from the diverse expertise within the community. Moreover, the transparent development process means that security measures are visibly, openly debated and implemented. This transparency lets administrators understand the security considerations behind each feature or update, making it easier to trust the browser’s security posture. This level of openness is invaluable in an era where trust is a critical security component. Control Over Updates and Features One of the primary challenges with proprietary browsers is the reliance on the vendor for updates and features. With Chromium, you have more control over these aspects, which is crucial for maintaining a secure environment. The initiative's open development model means that updates can be reviewed and customized to meet specific security requirements before deployment. For us Linux admins, this control is a significant advantage. It means we can apply updates that align with our organization's security policies and timelines rather than being at the mercy of a vendor's update cycle. We can also disable or enable features based on our security needs, ensuring the browser is as secure as possible for our specific environment. Enhanced Compliance and Auditing Compliance with security standards and the ability to conduct thorough audits are critical for any organization. Theopen-source nature of the "Supporters of Chromium-Based Browsers" initiative means that compliance and auditing processes can be more robust and community-verified. With the code openly available, verifying that the browser meets specific security standards and conducting comprehensive audits is easier. This means added assurance that your browsers comply with industry standards and that you can prove this compliance through thorough, transparent audits. The community-driven nature of the project ensures that compliance is not just about meeting the minimum standards but continuously evolving to address new security threats and challenges. Community and Industry Backing Major industry players' support of this initiative cannot be understated. Google, Meta, Microsoft, and Opera are providing financial backing and bringing their extensive expertise. This level of support ensures that the project will have the resources it needs to tackle significant security challenges and push the envelope regarding innovation. This backing means that the initiative is not a fringe project but a well-supported, mainstream effort with a higher probability of long-term success. These major players' combined resources and expertise ensure the project will benefit from the latest security research and development advancements. This is crucial for staying ahead of emerging threats and ensuring that the browsers you deploy are at the cutting edge of security technology. Our Final Thoughts on This Promising Chromium Browser Development Initiative The "Supporters of Chromium-Based Browsers" initiative by the Linux Foundation marks an exciting development for open-source communities and Linux security admins. By prioritizing open development, transparency, and community collaboration, this initiative promises browsers that are feature-rich but also secure and customizable. We have an incredible opportunity with this initiative to engage in an endeavor that brings together Open Source and security principles. Byplaying an active role, we can help shape the future of Chromium-based browsers so they meet the highest security standards tailored specifically for our environment. Seize this chance to enhance your browser security strategies and keep your systems safe in 2025 and beyond! . Participate in a collaborative effort aimed at bolstering web safety for Linux system operators while simplifying enhancements and upgrades.. Chromium browsers, open development, security collaboration, Linux admins, community driven. . Brittany Day
Jan 13, 2025
•
Organizations/Events
79
Linux securityOpenSSLcommunity engagementOpenSSL's Governance Changes Enhance Community Input and Security
On July 24, 2024, OpenSSL took an extraordinary step toward improving community engagement and realigning with its core values when it announced the implementation of a new governance framework and the launch of several projects under its mission statement. This event marks a historic moment for OpenSSL and Linux administrators worldwide who depend on this foundational technology for secure applications. . OpenSSL, the open-source cryptographic library providing secure communications for websites and applications, plays an essential role in the digital security ecosystem. Linux systems rely on it heavily to ensure data integrity, confidentiality, and authentication across many applications. OpenSSL's newly unveiled governance structure seeks to better reflect the project's longstanding mission by engaging community participation more actively while leading decision-making processes more inclusively. To help you better understand this initiative, I'll explain what has changed in OpenSSL's new governance model, the security implications for admins like you and me, and the project's plans for the future. What Is OpenSSL's New Governance Model? OpenSSL's revised governance framework introduces two independent, co-equal entities: OpenSSL Foundation and Corporation. They specialize in non-commercial and commercial communities and operate autonomously to meet community needs. With this arrangement, decisions align more effectively with community requirements than before. As part of the move to disband the OpenSSL Management Committee (OMC), governance now rests in the hands of two elected boards of directors who share responsibility, similar to what previously was held by OMC. Furthermore, Community Advisory Committees consisting of the Business Advisory Committee (BAC) and Technical Advisory Committee (TAC) will act as conduits for community input, signaling a shift toward more democratic governance practices. This structural reform brings significant advances in security and reliability forOpenSSL-powered systems. Two focused entities provide enhanced tailored support and developments in security protocols to create more secure Linux environments. Community Advisory Committees will ensure that Linux administrators' security needs and challenges find an efficient means of expression and resolution, keeping OpenSSL's roadmap aligned closely with today's ever-evolving security landscape. OpenSSL Expands its Mission to Encompass New Projects & Advance Linux Security At this juncture of its development, OpenSSL has also welcomed Bouncy Castle and cryptlib under its mission, adhering to their respective missions and values. Both projects are longstanding players in cryptography: Bouncy Castle provides open-source cryptographic APIs for Java and C# apps, while cryptlib offers a toolkit for embedding encryption services into applications. Bouncy Castle has proven invaluable for developers and Linux administrators. Thanks to its FIPS-certified solutions, long-term support releases, and quantum-ready cryptographic support, it bolsters the security posture of Linux systems that use Java or C# programming languages, giving administrators peace of mind knowing their systems contain state-of-the-art cryptography features. Similarly, the portability and support for multiple security protocols, including SSL/TLS , make cryptlib an indispensable asset in Linux security. It streamlines implementing world-class encryption services while improving application efficiency and reliability on Linux-based devices. Integrating Bouncy Castle and cryptlib into OpenSSL's mission and transitioning to its new governance model will herald a new era of innovation and security for Linux administrators. Access to diverse cryptographic tools and solutions helps enhance security standards while meeting common challenges more efficiently. Linux administrators can look forward to more secure, robust cryptographic implementations backed by community insights and innovations facilitated by the new governancemodel. These developments will increase security on Linux-based systems and foster an environment conducive to continued collaboration in the open-source security space. Final Thoughts: What's Next for OpenSSL? As OpenSSL embarks on its transformative journey, Linux administrators stand to reap significant benefits in terms of enhanced security, innovation, and community engagement. With advisory committees slated to be created and an OpenSSL user conference planned soon after this transition period commences, its future and effect on Linux security look bright. OpenSSL has welcomed these modifications, reinforcing its dedication to digital security in an increasingly connected world. For Linux administrators, staying abreast of these developments is crucial to keeping pace with cybersecurity's ever-evolving landscape. At LinuxSecurity, we commend OpenSSL's newly announced governance structure and projects, representing a transformative leap forward for cryptographic security and community engagement. . OpenSSL fosters collaboration and transparency, elevating security protocols for Unix-like platforms.. OpenSSL Governance Structure, Linux Security Framework, Cryptography Tools, Open Source Community. . Dave Wreski
Jul 31, 2024
•
Security Projects
79
open sourcesecurity toolssoftware securityOpenSSF: Collaborative Efforts in Software Security Development
Security is becoming an increasingly key piece of the open source puzzle amid industry-wide pushes to shift left and integrate security during early stages of application development. The Linux Foundation’s Open Source Security Foundation (OpenSSF), which encompasses Google’s Supply chain Levels for Software Artifacts (SLSA), is one example of how the open source community is working to improve software security through an ecosystem approach, vying for proactive handling of security by default. . OpenSSF brings together players like Cisco, GitHub, Google, VMware, and others to develop better security tools and practices for open source application development without bias toward a specific ecosystem or vendor. “It’s been very much a volunteer-driven effort involving all sorts of companies and individual software experts,” OpenSSF GM Brian Behlendorf said during a KubeCon press conference. . The Open Source Security Foundation (OpenSSF) coordinates collaboration between enterprises such as Microsoft and IBM to strengthen security frameworks in software engineering.. OpenSSF, Software Security, Security Tools, Open Source Development, Community Collaboration. . LinuxSecurity.com Team
Oct 26, 2021
•
Security Projects
76
community engagementcybersecurity eventhacker conferenceSalted Hash Day 2 Insights From DerbyCon 5.0 Conference
It . This post is being written at 0900, which is early for a hacker conference, but people are slowly starting to gather, as the picture shows. So far this weekend, Salted Hash has posted various conversation starters along with general updates, so today . On the second day of Salted Hash at DerbyCon 5.0, attendees engaged in rich discussions, sharing perspectives on cybersecurity innovations and challenges. Hacker Conference, DerbyCon, Cybersecurity Event, Networking Opportunities. . Anthony Pell
Mar 14, 2017
•
Organizations/Events
76
information securitytechnology trendscyber securityInsights from America's Biggest Hacker Conference on Cyber Culture
The hacker who has presided for 22 years over what is today the biggest hacker conference in the United States talks to TIME about Edward Snowden, Dorian Gray and hackers' changing role in society. . For one weekend every year, thousands of the world The link for this article located at Time is no longer available. . As technology reshapes our lives, the insights from the founder of the largest hacker conference in the U.S. highlight critical truths about our changing world. Hacker Conference, Cyber Culture, Information Security, Technology Trends. . Dave Wreski
Aug 13, 2014
•
Organizations/Events
76
academic collaborationcommunity engagementopen source eventA Journey to The Ottawa Linux Symposium: Community and Collaboration
I do not often do this, but old friend is in trouble. Please stay with me as I tell this story. It was around the year 2002, and I was in Brazil. I met two young college students who were very interested in Linux, and who impressed me with their enthusiasm and willingness to help others. . I asked them what they would really like to do, and their answer was to attend the Ottawa Linux Symposium (OLS) in Ottawa, Canada and to meet Linus Torvalds. I was not surprised about either desire. OLS had been going on for a number of years, taking the place of the Raleigh Linux Expo that had been run by Red Hat. But while the last Linux Expo was more like a hippie be-in, with people in bare feet throwing Frisbees on the lawn of Duke University, OLS was a conference that required papers to be written about the presentations being done. The link for this article located at Linux Magazine is no longer available. . In a charming college town, students Emma and Raj dream of attending the Ottawa Linux Symposium to meet Linus Torvalds, fueling their passion for open-source.. Ottawa Linux Symposium, Open Source Events, Linux Community, OLS Experience. . Dave Wreski
Jul 30, 2014
•
Organizations/Events
Get the latest News and Insights
Get the latest Linux and open source security news straight to your inbox.
Community Poll
Should Linux servers automatically install security updates?
Trending News
Search Topics
Powered By
Linux Security - Your source for Top Linux News, Advisories, HOWTOs and Feature Releases
QUICK LINKS
subscribe to newsletters!
Like staying secure? So do we.
Sign up for updates, tips, and alerts!