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...
67
networkingredhatipsecFreeS/WAN Weekly Report: IPsec Implementation on Zaurus and RedHat Issues
This issue, we have reports of FreeS/WAN running on the Sharp Zaurus (item 1) and having a few small issues with RedHat 8.0 (item 2). Claudia Schmeing has posted a new revision of our interoperation document (item 3). Item 4 has a great discussion on the use of routing protocols with FreeS/WAN.. . . . This issue, we have reports of FreeS/WAN running on the Sharp Zaurus (item 1) and having a few small issues with Red Hat 8.0 (item 2). Claudia Schmeing has posted a new revision of our interoperation document (item 3). Item 4 has a great discussion on the use of routing protocols with FreeS/WAN. . Investigate the implementations of FreeS/WAN on the Sharp Zaurus, while delving into routing strategies and addressing RedHat complications.. IPsec Security, FreeS/WAN Integration, Zaurus Connectivity. . LinuxSecurity.com Team
Oct 16, 2023
•
Cryptography
81
data securityencryptionipsecImproving Server Communication Performance With IPSEC Instead Of OpenVPN
Often we need to secure communication channels, not for remote workers, but for server-to-server communication. Backups, for example, come to mind. It may be fine to use SSH or stunnel to ship data securely, but when performance is required and encryption cannot slow down communication, something else is necessary. OpenVPN is easy to configure, but it may not be sufficient.. If data is critical enough to ship off-site in real time, chances are it's valuable data, and should be encrypted for transit. Real-time data replication that databases often use, requires a fast enough network connection to avoid slowing down the local server. Disk block replication, i.e. DRBD, is even more sensitive to overhead when running synchronously to guarantee data integrity. Administrators will often configure a quick VPN connection for security, but then realize they've just compromised performance. The link for this article located at Enterprise Networking Planet is no longer available. . If data is critical enough to ship off-site in real time, chances are it's valuable data, and should. often, secure, communication, channels, remote, workers, server-to-server. . LinuxSecurity.com Team
Oct 22, 2009
•
Privacy
74
network securityencryptionremote accessEffective VPN Setup For Remote Workers Securing Networks
Locking down the network and patrolling the perimeter is a never-ending job. Still, it feels good to get through another shift on the Forbidden Planet without an invisible force penetrating your shield and setting off alarms. But there's a change: now, other humans want to work from their home worlds -- but by mind alone, over the computer screen. It's up to you to create for them a safe passage (one that won't have Robby the Robot all stirred up and carrying Anne Francis around like a rag doll) and to make sure the Krell don't come sneaking in, under the fence, behind the newcomers. . In other words, you need to let the right people into your network -- telecommuters and other people working remotely -- while continuing to protect the company from criminals. What to do? The Number One Answer: A Sit-Down VPN The answer that helps administrators sleep most securely is a fixed Virtual Private Network (VPN). A VPN uses end-to-end encryption to carve out a private tunnel over the public network. The most secure VPN is the traditional arrangement with the telecommuter coming from a fixed site, ideally using a managed, corporate device, and terminating in a secure, private network on either side. Quite a bit of effort can go into setting up this arrangement; you need to see that hardware, software, and settings, as well as authentication, are set up perfectly and maintained on both ends, despite user changes to software, firmware, and hardware, but the security can be worth the trouble. Don't let this next bit scare you away: After the act with all the acronyms, you'll have the secret of the monster sneaking past the alarms, and everything lightens up. Let's throw out some protocols -- literally. There are three or four at this end of the pool. Only one from this group is secure enough to take seriously: IPSec, especially in conjunction with L2TP. The link for this article located at Rebecca Rohan is no longer available. . Safeguard your network by implementing VPN settings that enable safe access fortelecommuters while shielding your system from potential risks.. Remote Access, Virtual Private Network, IPSec, Network Management, Telecommuting. . Joe Shakespeare
Jan 10, 2005
•
Network Security
79
encryptionsecuritynetworkingIPsec Implementation In Linux Kernel 2.6: Securing VPN Communication
IPsec is an addition to IP protocol that allows authentication and encryption of IP datagrams. It is defined in detail in IETF RFCs 2401, RFC 2402, RFC 2406 and RFC 2407 (see Resources). IPsec can be used to secure a rather wide range of scenarios; one of its best-known usages is creating virtual private networks (VPNs). . . .. IPsec is an addition to IP protocol that allows authentication and encryption of IP datagrams. It is defined in detail in IETF RFCs 2401, RFC 2402, RFC 2406 and RFC 2407 (see Resources). IPsec can be used to secure a rather wide range of scenarios; one of its best-known usages is creating virtual private networks (VPNs). A VPN is a secure, private tunnel between two sub-networks using encrypted communication over the Internet. FreeS/WAN has been the main IPsec implementation for Linux for a long time. Unfortunately, FreeS/WAN has never been integrated into the Linux kernel itself. Instead, the new native kernel IPsec implementation is based on the KAME project, a part of the UNIX/BSD family. The USAGI project used the BSD code from the KAME project as a base for integrating IPsec into the Linux kernel. KAME's user-space tools, specifically setkey and Racoon, have been ported to Linux by the IPsec-tools Project (see Resources). The link for this article located at linuxjournal.com is no longer available. . IPsec safeguards IP packets by employing encryption and authentication, enabling secure VPNs and enhancing network safety.. ipsec security, vpn encryption, linux kernel ipsec, networking protocols, data encryption. . LinuxSecurity.com Team
Oct 13, 2004
•
Security Projects
79
ipsecsecure communicationopen source projectNovell Sponsors Openswan Project for Secure IPsec VPN Standards
Novell announced that it is sponsoring and contributing to the popular open source Linux implementation of the IP security (IPsec) standard development project, Openswan. The open source project brings all of the features needed for building and deploying secure commercial grade virtual private networks (VPNs) to Linux. . . .. Novell announced that it is sponsoring and contributing to the popular open source Linux implementation of the IP security (IPsec) standard development project, Openswan. The open source project brings all of the features needed for building and deploying secure commercial grade virtual private networks (VPNs) to Linux. Secure VPNs are increasingly being deployed in the enterprise to provide a high level of security. IPsec is standardized protocol from the Internet Engineering Task Force (IETF) that provides a standard way of transmitting services which allow users to build secure tunnels through untrusted networks. Information is encrypted by the IPsec gateway machine and decrypted on the other end. IPsec-certified products are interoperable across vendor product lines, and provide security. Salt Lake City-based Novell also announced today that its BorderManager product is certified on the latest IPsec interoperability tests from ICSA Labs. This testing demonstrates interoperability and open standards compliance. Novell's BorderManager is part of the company's Nsure secure identity management solution. The link for this article located at desktoplinux.com is no longer available. . Oracle backs a collaborative open-source initiative for WireGuard, enhancing secure connections for businesses by adhering to top-notch protocols.. Open Source, IPsec, VPN Security, Linux Protocols, Novell Contributions. . LinuxSecurity.com Team
Jun 18, 2004
•
Security Projects
74
network securityremote accessipsecIPSec And SSL VPN: Evaluating The Best Remote Access Option
By implementing a VPN, a company can provide access to the internal private network to clients around the world at any location with access to the public Internet. It erases the administrative and financial headaches associated with a traditional leased line wide-area network (WAN) and allows remote and mobile users to be more productive. . . .. By implementing a VPN, a company can provide access to the internal private network to clients around the world at any location with access to the public Internet. It erases the administrative and financial headaches associated with a traditional leased line wide-area network (WAN) and allows remote and mobile users to be more productive. Best of all, if properly implemented, it does so without impacting the security and integrity of the computer systems and data on the private company network. Traditional VPN's rely on IPSec (Internet Protocol Security) to tunnel between the two endpoints. IPSec works on the Network Layer of the OSI Model- securing all data that travels between the two endpoints without an association to any specific application. When connected on an IPSec VPN the client computer is "virtually" a full member of the corporate network- able to see and potentially access the entire network. SSL VPN's have been gaining in prevalence and popularity; however they are not the right solution for every instance. Likewise, IPSec VPN's are not suited for every instance either. Vendors are continuing to develop ways to expand the functionality of the SSL VPN and it is a technology that you should watch closely if you are in the market for a secure remote networking solution. For now, it is important to carefully consider the needs of your remote users and weigh the pros and cons of each solution to determine what works best for you. The link for this article located at About.com is no longer available. . Utilizing a VPN allows safe connectivity to corporate networks for off-site users, boosting efficiency and safeguarding data.. VPN Implementation, SecureTunneling, Remote Network Access, Network Protection. . Anthony Pell
Nov 17, 2003
•
Network Security
67
secure connectionsipsecfreeswanReliable LAN-to-LAN Connections with FreeS/WAN's X509 Patch
In countries where a private or semi-public WAN is something not every company can afford, the Internet is the only option available to connect all of those remote offices. The obvious problems are this is a public network and, in most . . . . In countries where a private or semi-public WAN is something not every company can afford, the Internet is the only option available to connect all of those remote offices. The obvious problems are this is a public network and, in most cases, we don't get a static IP address. We know that sending data through the Internet is like talking to somebody in an elevator--everybody just can't help hearing what you're saying. So, not encrypting the data is not an option. Many types of tunnels can be used and VPNs can be put together in many ways, but the IPsec implementation of Linux (FreeS/WAN) is by far the most secure and compatible way to do it. In this article, I explain how to establish LAN-to-LAN tunnels using the x509 patch and only one static IP address. I also tell you two ways to get around the four tunnel inconvenience. FreeS/WAN has two main parts: the IPsec patch for the kernel (KLIPS) that implements AH (authentication header), ESP (encapsulating security payload) and packet handling within the kernel; and the userland tools (pluto). Pluto implements IKE (internet key exchange), which negotiates the many connections with other systems. The link for this article located at LinuxJournal is no longer available. . In countries where a private or semi-public WAN is something not every company can afford, the Inter. countries, where, private, semi-public, something, every, company, afford, inter. . LinuxSecurity.com Team
Jul 15, 2003
•
Cryptography
67
network securitysecurity protocolsipsecUnderstanding IPSec Security Levels for Safe Packet Transmission
Explaining IPSec, different levels of security and how to be safe sending and receiving packets over the network. .. VPNs (virtual private networks, i.e., private networks deployed over a public packet infrastructure) are definitely emerging as the solution of choice for the interconnection of distant offices belonging to the same company.. . .. Explaining IPSec, different levels of security and how to be safe sending and receiving packets over the network. .. VPNs (virtual private networks, i.e., private networks deployed over a public packet infrastructure) are definitely emerging as the solution of choice for the interconnection of distant offices belonging to the same company. Unfortunately, IP packets carry our precious data in a clear form that is easily intercepted by malicious users. Doing this on a common Linux-based PC is actually quite easy, provided that one has access to the network segment over which the desired packets are traveling. Several different solutions exist that allow us to cope with this problem, each operating at a different level of abstraction. In this article, we will discuss the differences between and purposes of application-level security, socket-level security and network-level security. The link for this article located at Linux Journal is no longer available. . Explaining IPSec, different levels of security and how to be safe sending and receiving packets over. explaining, ipsec, different, levels, security, sending, receiving, packets. . LinuxSecurity.com Team
Sep 09, 2002
•
Cryptography
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!