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 -2 articles for you...
77
security advisorysecurity issuebuffer overflowDisabling Sendmail: Address Buffer Overflow Risk on UNIX Systems
The Sendmail buffer overflow exploit announced in March will almost certainly be programmed into an automated worm within the next six months. Such a worm could do for UNIX systems what Code Red did to the Windows world -- simply because there are so many potentially vulnerable UNIX systems on the network today. . . .. The Sendmail buffer overflow exploit announced in March will almost certainly be programmed into an automated worm within the next six months. Such a worm could do for UNIX systems what Code Red did to the Windows world -- simply because there are so many potentially vulnerable UNIX systems on the network today. Shutting off the Sendmail daemon on 99.9% of the systems in your environment would greatly reduce the potential impact of such a worm. The Role of the Sendmail Daemon When I discuss security issues with systems administrators, I find that many of them are confused about the need for a running Sendmail daemon on their systems. This confusion is understandable since, for at least the last two decades, the commercial UNIX vendors have been shipping their operating systems with active Sendmail daemons in the default install. Most administrators simply assume that this daemon is necessary for the users and automated processes running on the system to be able to emit email from the machine. The reality, however, is that the Sendmail daemon on a machine is only responsible for two things: Listening on port 25/tcp for incoming messages from outside of the machine Flushing the local queue of unsent messages on a periodic basis Having a Sendmail daemon listening on 25/tcp opens the system up for remote exploits such as the recently announced buffer overflow issue. Note that the system only needs to be listening on 25/tcp if it is actively expecting to receive email messages from other systems. In fact, the only systems on the network that receive external email are the machines that are acting as mail servers and mail relays. A given site will typically only have a small handful ofthese machines (many of which are Windows machines running Exchange anyway). The other 99.9% of the systems on the network are email "clients" -- that is they may emit email messages from time to time, but never expect to receive a message from another machine. On these machines, it is probably best to simply disable the Sendmail daemon altogether in order to eliminate the potential for remote exploits. The link for this article located at SysAdmin is no longer available. . Reduce vulnerabilities stemming from the Sendmail buffer overflow by disabling Sendmail functionalities on non-essential systems to bolster security.. Sendmail Exploit, UNIX Security, Buffer Overflow Prevention, Email Daemon Risks. . LinuxSecurity.com Team
Jun 09, 2003
•
Server Security
77
application securitysecurity riskdevelopment practicesStrategies To Avoid Security Holes In CGI Script Development
This article is the first one in a series about the main types of security holes in applications. We'll show the ways to avoid them by changing your development habits a little. This set of articles shows methods which can be . . . . This article is the first one in a series about the main types of security holes in applications. We'll show the ways to avoid them by changing your development habits a little. This set of articles shows methods which can be used to damage a Unix system. We could only have mentioned them or said a few words about them, but we prefer complete explanations to make people understand the risks. Thus, when debugging a program or developing your own, you'll be able to avoid or correct these mistakes. For each discussed hole, we will take the same approach. We'll start detailing the way it works. Next, we will show how to avoid it. For every example we will use security holes still present in wide spread software. . Enhance security in your web applications by mastering strategies to prevent vulnerabilities, particularly in CGI scripts, while adhering to optimal coding standards.. Application Security, CGI Scripts, Development Best Practices. . LinuxSecurity.com Team
Dec 10, 2001
•
Server Security
83
security advisoryremote accessmalwareVuln-Dev Alert: Trojan Horse Impacts Unix Systems - Security Risk
On Wednesday, the 14,300-strong subscribers to a popular security list known as Vuln-Dev received what may have appeared a rare treat: a message to the list containing source code to a program that gave the user full control of a remote Unix system. But as some Vuln-Dev readers, many of whom are system administrators for businesses, painfully learned, the program was a Trojan horse, and if compiled and run, could delete most of the files on the user's computer.. . .. On Wednesday, the 14,300-strong subscribers to a popular security list known as Vuln-Dev received what may have appeared a rare treat: a message to the list containing source code to a program that gave the user full control of a remote Unix system. But as some Vuln-Dev readers, many of whom are system administrators for businesses, painfully learned, the program was a Trojan horse, and if compiled and run, could delete most of the files on the user's computer. List member Jason Parker told Newsbytes he glanced over the code before compiling it, decided it looked legitimate, and ran it Thursday on the test account of a system. "I lost everything in the home directory, including information I would rather not have lost, but that's the price you pay for trusting," said Parker, who has since replaced the front page of his site with an obscene comment about Meinel. The link for this article located at Newsbytes is no longer available. . Cybersecurity professionals are alerting users about a malicious Trojan horse software that deceptively claims to provide remote access to Linux servers.. Trojan Horse, Unix Control, Security Risks, Source Code, Vuln-Dev. . LinuxSecurity.com Team
Sep 22, 2001
•
Hacks/Cracks
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