Network Security
system security Linux network
system security Linux network The romanticized image of the digital nomad – a laptop on a sun-drenched balcony – rarely accounts for the actual friction of maintaining a professional development environment on the move. . The friction is amplified with Linux. We are looking for a setup that respects our kernel configurations, handles volatile network handovers, and maintains a strict security posture without the hand-holding of a consumer-grade OS – so, put simply, more than just a laptop and a sunny deck. The hardware is...
May 26, 2026
Server Securityopen-source Linux administration
open-source Linux administration Cron has existed in Unix and Linux environments for decades, handling backups, cleanup scripts, patching jobs, log rotation, monitoring tasks, and other maintenance work that administrators do not want to run manually. Most Linux servers rely on it constantly, which is exactly why attackers continue abusing it for persistence after a system has already been compromised. . Persistence through cron is not complicated. Attackers do not need a rootkit or advanced malware framework to maintain...
May 25, 2026
Vendors/Productssecurity breach linux
security breach linux A major internal repository breach at GitHub has exposed a critical and overlooked blind spot in Linux supply chain security. Kernel exploits, exposed SSH services, weak firewall rules, and vulnerable daemons dominated the Linux threat model for years, and in many environments, they still matter. But recent supply-chain incidents involving GitHub ecosystems, npm packages, and malicious developer tooling point somewhere else entirely: the developer workstation. . The breach matters because...
May 21, 2026
Security Trends access control multi-tenant
access control multi-tenant Linux administrators often face an ugly choice in the cloud: prioritize convenience and cost-efficiency by sharing infrastructure, or sacrifice those benefits for the sake of total isolation. Most modern Linux workloads don't live on their own private servers anymore. They live in shared environments like Kubernetes clusters, where multiple teams and services run side-by-side. It sounds efficient, and it usually is. . But cloud isolation isn't as ironclad as it looks on the diagram. If you...
May 21, 2026
Vendors/Productsincident response cloud security
incident response cloud security Managed Extended Detection and Response (MXDR) has become one of the most sought-after security services in the enterprise market — and with good reason. It promises the holy grail: broad visibility across endpoints, network, cloud, email, and identity, combined with the 24/7 human expertise most organizations simply cannot build in-house. . However, the rapid growth of the market has produced a wide range of providers whose capabilities vary considerably beneath the surface. Choosing the...
May 19, 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
What got you started with Linux?
Loading...
Explore Latest Linux Security news
We found 3 articles for you...
79
open sourcecode qualityproprietary softwareOpen Source Defect Rates vs Proprietary Software: Coverity Analysis
Forget bad headlines generated by the Heartbleed flaw, when it comes to code defects open source is still well ahead of proprietary software, generating fewer coding defects for every size of project, according to a new analysis by scanning service Coverity.. The firm's figures from its Scan Service show that for the C/C++ projects submitted for assessment during 2013, 493 proprietary projects representing 684 million lines of code generated an average defect rate of 0.72 per 1,000 lines of code. The link for this article located at Network World is no longer available. . Research by Coverity indicates that open source software consistently outperforms proprietary software, particularly in terms of code quality and defect prevalence.. Code Quality, Open Source Software, Software Analysis. . LinuxSecurity.com Team
Apr 18, 2014
•
Security Projects
79
security advisorysecurity concernsystem integrityAlcotest 7110 MKIII-C Advisory: Significant Software Flaws Uncovered
This is an excellent lesson in the security problems inherent in trusting proprietary software: After two years of attempting to get the computer based source code for the Alcotest 7110 MKIII-C, defense counsel in State v. Chun were successful in obtaining the code, and had it analyzed by Base One Technologies, Inc. Draeger, the manufacturer maintained that the system was perfect, and that revealing the source code would be damaging to its business. They were right about the second part, of course, because it turned out that the code was terrible.. The link for this article located at is no longer available. . Analysis of vulnerability concerns within closed-source applications and defects discovered in Alcotest 7110 MKIII-C's codebase.. Alcotest Security Flaws, Proprietary Software Issues, Source Code Analysis. . LinuxSecurity.com Team
May 14, 2009
•
Security Projects
82
cybersecurityopen sourcesoftware developmentNSA Initiatives for Open Source and Proprietary Software Security
NSA initiatives in enhancing software security cover both proprietary and open source software, and we have successfully used both proprietary and open source models in our research activities. NSA's work to enhance the security of software is motivated by one simple consideration: use our resources as efficiently as possible to give NSA's customers the best possible security options in the most widely employed products. The objective of the NSA research program is to develop technologic advances that can be shared with the software development community through a variety of transfer mechanisms. NSA does not favor or promote any specific software product or business model. Rather, NSA is promoting enhanced security. The NSA has new page on their site with information on a tons of security resources for both open source and proprietary software. Check it out you might learn something new.. The link for this article located at nsa.gov is no longer available. . The link for this article located at nsa.gov is no longer available.. software, initiatives, enhancing, security, cover, proprietary, source. . Bill Locke
Aug 29, 2008
•
Government
78
software competitionproprietary softwaregovernment softwareMicrosoft Expands Source Code Access For Government Organizations
Microsoft Corp. is expanding a program to give government organizations access to some of its tightly guarded software blueprints amid growing competition from rivals who make such source code freely available. . . .. Microsoft Corp. is expanding a program to give government organizations access to some of its tightly guarded software blueprints amid growing competition from rivals who make such source code freely available. Beginning Monday, Microsoft will offer more than 60 governments and international organizations the option of viewing the proprietary source code for the latest version of its ubiquitous Office software, including the Outlook e-mail program, Microsoft Word and Excel spreadsheet application. The link for this article located at Canadian Press is no longer available. . Apple is offering certain educational institutions access to unique code frameworks for its iWork productivity suite.. Microsoft Code Access, Government Software Program, Source Code Access, Office Applications. . LinuxSecurity.com Team
Sep 20, 2004
•
Vendors/Products
78
open sourcecommunity impactsoftware controlSun Microsystems: Java Remains Proprietary Amid Open Source Push
This can be considered closure to an issue that could have affected the entire open-source community. The idea of making Java the basis of a secure, open-source development platform is simply not viable right now. . . .. Despite urging from competitors and open source advocates, Sun Microsystems Inc. of Santa Clara, Calif., will not open the source to its Java programming language anytime soon, said Sun CEO Scott McNealy during a news conference at the 2004 FOSE conference. "We're trying to understand what problem does it solve that is not already solved," McNealy said. Last month Eric Raymond, noted open source programmer and president of the Open Source Initiative advocacy group, posted an open letter to McNealy calling for Sun to make Java open source. "Sun's insistence on continuing tight control of the Java code has damaged Sun's long-term interests by throttling acceptance of the language in the open-source community, ceding the field (and probably the future) to scripting-language competitors like Python and Perl," Raymond wrote. Java is an object-oriented language developed by Sun. Written originally for embedded devices, Java was designed to allow a single program to be written once and be able to run on multiple platforms without modification, through the use of the software-based Java Virtual Machine. Although Sun maintains Java is an open implementation, allowing other software manufacturers to license the code and build competing Java-based products, the company maintains control over what changes can be made to the language. One advantage of keeping Java under its own control is that competing factions break the language into incompatible versions, McNealy said. He noted that Linux already suffers from this problem. The leading Linux vendor, Red Hat Inc. of Raleigh, N.C., has already introduced features in its own version of Linux that make it incompatible with other versions. Since Linux is open source, Red Hat was free to build its own version of the operating system. In contrast, when MicrosoftCorp. of Redmond, Wash., tried to introduce features into its own version of Java that wouldn't work in non-Windows systems, Sun successfully blocked the changes through legal means, McNealy said. The link for this article located at GovernmentComputerNews is no longer available. . Scott McNealy explains the reasoning for Java's proprietary design, emphasizing its impact on the software development landscape amidst the rising calls for open source options. Java Development, Software Control, Open Source Advocacy. . LinuxSecurity.com Team
Mar 25, 2004
•
Vendors/Products
81
security assessmentsoftware innovationproprietary softwareDoD Procurement: Balancing Open Source And Proprietary Software
The Initiative for Software Choice, a software industry trade group whose members include Microsoft, Intel and Cisco, has advised the U.S. Department of Defense not to adhere to a policy that promotes open source software at the expense of proprietary software. . . . . The Initiative for Software Choice, a software industry trade group whose members include Microsoft, Intel and Cisco, has advised the U.S. Department of Defense not to adhere to a policy that promotes open source software at the expense of proprietary software. The group has issued a report arguing that the DoD's evaluation of software purchases should not be influenced by "a preconception that open source software is somehow inherently more secure." "ISC is against government policy that restricts procurement to any kind of software," ISC executive director Bob Kramer told NewsFactor. He noted that the group has no prejudice against any software, but that government procurement policies "should focus on obtaining the best software to solve the problem." The ISC Mission The Washington, D.C.-based ISC was founded in May. The group states it is "dedicated to the principle that governments should procure their software products on their merits rather than categorical preferences." Therefore, its goal is to "educate policymakers about the need to remain neutral about the governmental purchase of software." Toward that goal, the ISC recently issued a report that countered another report written by defense contractor MITRE. The MITRE report noted that open source software "plays a more critical role in the [DoD] than has generally been recognized," and that the DoD has 115 open source applications with 251 identified uses. It then concluded that open source products are a viable alternative to proprietary products made by Microsoft and others, and recommended that they be used more widely. The ISC Response The ISC strongly contested MITRE's conclusions, stating that MITRE's preference for open source stymies software innovation. Thebest way to promote innovation, according to the ISC, is to "ensure that customers -- both public and private -- have a broad range of choices in their software purchasing decisions." In particular, the ISC disagreed with the MITRE report's findings that open source products allow "early and rapid closure of security holes ... [which is] generally impractical in closed source products." In arguing against this finding, the ISC stated that "no single development mode inherently produces safer, more secure software." GPL Issues The ISC report also found fault with MITRE's conclusions about the General Public License (GPL). The GPL , which is used by some programmers in the open source community, requires developers to make their source code publicly available if they modify a program already licensed under the GPL. The ISC noted that, if there were a government policy requiring all software purchases to be licensed under the GPL, it would entail significant loss for commercial software developers. These developers "expend significant resources walling off their proprietary intellectual property," the report said. ISC pointed to MITRE's findings that more than 50 percent of the DoD's open source products are GPL-based, and that if proprietary developers were required to use the GPL, it would "foreclose proprietary companies ... from further developing and commercializing the results." . The Initiative for Software Choice, a software industry trade group whose members include Microsoft,. software, initiative, choice, industry, trade, group, whose, members, include, microsoft. . LinuxSecurity.com Team
Dec 02, 2002
•
Privacy
82
security advisoryelectronic votinghacking riskSecurity Risks In Electronic Voting: Proprietary Software Concerns
As Americans go to the polls today, a record number of counties -- almost one fifth by some estimates -- will be tallying the votes on electronic voting machines. But some experts worry that despite rigorous testing, the machines may not be as secure as their makers promise. . . .. As Americans go to the polls today, a record number of counties -- almost one fifth by some estimates -- will be tallying the votes on electronic voting machines. But some experts worry that despite rigorous testing, the machines may not be as secure as their makers promise. "People have jumped on the electronic voting bandwagon, thinking that will solve the problems," said Avi Rubin, a technology security expert and researcher at AT&T Labs in New Jersey. "But these systems are largely untested." The problem, say critics, is that the software which runs the machines is proprietary, and therefore not open to public scrutiny. Without scientists being able to freely analyze the systems, election officials may be leaving themselves open to the possibility of hacking, vote tampering or incorrect calculations. The link for this article located at CNN is no longer available. . Worries grow regarding the prevalence of digital ballot systems, as cybersecurity analysts highlight dangers associated with closed-source applications.. Electronic Voting,Safety Concerns,Hacking Risks,Security Issues. . Anthony Pell
Nov 05, 2002
•
Government
78
open sourcesoftware securitycoding practicesOpen Source vs Proprietary Software: Insights on Security Perspectives
Jeremy Allison goes against a Microsoft security specialist in this open source vs proprietary debate. "I believe that the open source development model does create software with significantly fewer exploitable holes than proprietary software. ... I know that programmers of proprietary . . . . Jeremy Allison goes against a Microsoft security specialist in this open source vs proprietary debate. "I believe that the open source development model does create software with significantly fewer exploitable holes than proprietary software. ... I know that programmers of proprietary software leave holes and take more liberties than open source programmers. The reasons are simple: Their management and marketing departments are screaming for the code to ship, doing it right is harder than doing it quickly and, after all, they think, who is going to know? I've been in this situation myself. On the other hand, most open source software is written by people for whom programming is not a chore. It's a craft, and they take great pride in doing their work properly. Away from the demands of marketing and management, they are able to create the code that they want to write, not the code that will make the most money. The difference in the quality of the code produced by the two methods is staggering." The Microsoft side counters with "Commercial software tends to be more secure than open source software, for simple economic reasons. Simply put, you get what you pay for. Commercial development organizations have a powerful motivation to get security right: Their livelihoods depend on it. That's why commercial software firms use advanced tools and follow processes that leverage knowledge of known security flaws to drive "lessons learned" into new code. Commercial software firms not only employ people who are dedicated and passionate about security, they also pay them to do the hard, tedious work - including testing - that's not especially interesting to most open source volunteers." The link forthis article located at Interactive Week is no longer available. . Delving into the ongoing security discourse surrounding open source versus proprietary software, featuring perspectives from industry specialists.. Open Source Security, Proprietary Software, Security Perspectives, Exploitable Holes, Software Development. . LinuxSecurity.com Team
Jul 17, 2001
•
Vendors/Products
Get the latest News and Insights
Get the latest Linux and open source security news straight to your inbox.
Community Poll
What got you started with Linux?
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!
Discover faster search, smarter navigation, and deeper Linux security insights. Read More