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 -1 articles for you...
79
patch managementsoftware updatessystem maintenanceThe Importance Of Regular Software Updates For Open Source Security
Palamida, an open-source risk management company, believes in open source. But at the same time, its corporate code audits of more than 500 million lines of code has found time and again "specific open-source projects inside mission critical systems that had not been patched" with most recent updates. Read on for an interesting account of what happens when you don't keep up with the times. A great point Palamida gets across is the fact that even though you are using a great open source tool does not substitute not keeping it up to date.. The link for this article located at Linux Watch is no longer available. . The link for this article located at Linux Watch is no longer available.. palamida, open-source, management, company, believes, source. . LinuxSecurity.com Team
Mar 26, 2008
•
Security Projects
77
security patchpatch managementcost analysisUnderstanding Patch Management Costs And IT Resource Challenges
Security and vulnerability patching has become one of the top concerns for IT managers, but has also left many IT teams fighting a losing battle as the job of patching competes with day-to-day system maintenance and security tasks. . The patching issue became a more prominent problem for businesses worldwide in 2003 when the Slammer worm was unleashed on the Internet. In the first minute after it started spreading, Slammer doubled the number of web servers it infected every eight seconds. Within 10 minutes, 90% of all vulnerable machines had been infected – leaving businesses with a £500m bill to fix the havoc Slammer created. Yet the patch to fix the vulnerability that Slammer exploited had been available for six months. If the majority of those infected had patched their systems, Slammer would have been a minor blip. So why aren’t businesses catching on to patching? The bottom line is that many IT teams simply do not have the resources or time. Just researching the 4,000+ vulnerabilities published by security monitoring body CERT in the last year would demand hundreds of man-hours. And although an IT staff may be online regularly to see what patches are released, they cannot be 100 percent sure that all systems are properly patched. Then there’s the cost issue. Recent research from analysts at The Yankee Group found that it can cost as much as $1 million to manually deploy a single patch in a 1,000-node network environment. The costs include the manual labour involved in fixing problems and system downtime while patches are being applied. The link for this article located at Security Park is no longer available. . Updating software consistently poses significant challenges for IT departments; financial constraints and limited manpower obstruct prompt remediation of at-risk platforms.. Patch Management,Vulnerability Updates,Resource Allocation. . LinuxSecurity.com Team
Apr 20, 2005
•
Server Security
67
OpenSSHsystem maintenanceremotely upgradeComprehensive Step-by-Step Guide for Safe Remote OpenSSH Upgrade
Brian Hatch, author of Hacking Linux Exposed, wrote in to point out his step-by-step guide for safely upgrading OpenSSH. "Most folks don't realize that you can kill off the sshd server process (the one that forks off copies to handle incoming connections) without killing off any existing connections.. . .. Brian Hatch, author of Hacking Linux Exposed, wrote in to point out his step-by-step guide for safely upgrading OpenSSH. "Most folks don't realize that you can kill off the sshd server process (the one that forks off copies to handle incoming connections) without killing off any existing connections. That means you can log in, kill off the server process, and still work on the system until you log out. Instead, most folks think you need to upgrade and reboot so the changes take effect. This is not the case. However, if you don't take a few precautions, then you could find yourself in the unfortunate situation where you've killed the old process and accidentally logged out (or, more likely, kill all sshd processes) before starting the new daemon. . Upgrading OpenSSH remotely without downtime or losing connections is possible with thorough planning. Follow this guide for a seamless upgrade process. OpenSSH Upgrade, Remote Administration, Linux Server. . LinuxSecurity.com Team
Jun 26, 2002
•
Cryptography
77
risk managementsecurity practicessecurity guidanceTen Immutable Security Principles: Timeless Guidance For Protection
This Microsoft article does a good job of outlining a list of security issues that no patch can fix. Only dilligence in maintaining your systems can ensure you're systems are as secure as possible. "In other cases, the reported problems simply . . . . This Microsoft article does a good job of outlining a list of security issues that no patch can fix. Only dilligence in maintaining your systems can ensure you're systems are as secure as possible. "In other cases, the reported problems simply result from a mistake someone made in using the product. But many fall in between. They discuss real security problems, but the problems don't result from product flaws. Over the years, we've developed a list of issues like these, that we call the Ten Immutable Laws of Security. Don't hold your breath waiting for a patch that will protect you from the issues we'll discuss below. It isn't possible for Microsoft - or any software vendor - to "fix" them, because they result from the way computers work. But don't abandon all hope yet - sound judgment is the key to protecting yourself against these issues, and if you keep them in mind, you can significantly improve the security of your systems." The link for this article located at Microsoft.com [newsforge] is no longer available. . Implement the principle of least privilege to ensure users have only necessary access, greatly reducing breach damage potential. Immutable Laws, Security Practices, System Maintenance, Risk Management. . LinuxSecurity.com Team
Nov 06, 2000
•
Server Security
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!