Audit Linux privileges now to limit compromise, escalation, and system-wide damage. Review Linux Privileges×
Security Vulnerabilities 
cisa kev vulnerability prioritization
cisa kev vulnerability prioritization Most Linux teams don't struggle to find vulnerabilities anymore. They struggle to decide which ones deserve attention first. Between daily scanner results, vendor advisories, and hundreds of new CVEs each month, the challenge isn't visibility—it's prioritization. . To solve this, organizations typically lean on the National Vulnerability Database (NVD) and CISA’s Known Exploited Vulnerabilities Catalog. But these aren’t competing lists. They answer two entirely different questions. While the...
Jul 22, 2026
Desktop Securitysecurity 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
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 6 articles for you...
67
cryptographyNSAkey exchangeNSA Claims On Breaking Diffie-Hellman Key Exchange Through Precomputation
The Internet is abuzz with this blog post and paper, speculating that the NSA is breaking the Diffie-Hellman key-exchange protocol in the wild through massive precomputation. . I wrote about this at length in May when this paper was first made public. (The reason it's news again is that the paper was just presented at the ACM Computer and Communications Security conference.) . Discussions reveal that the NSA may undermine the Diffie-Hellman key exchange by leveraging its computational power for precomputing keys, raising security concerns.. Diffie-Hellman Key Exchange, NSA Cybersecurity, Cryptography Insights. . LinuxSecurity.com Team
Mar 14, 2017
•
Cryptography
82
network securitycryptographic weaknesskey exchangeWarning: NSA Can Eavesdrop On Trillions Of Encrypted Connections
For years, privacy advocates have pushed developers of websites, virtual private network apps, and other cryptographic software to adopt the Diffie-Hellman cryptographic key exchange as a defense against surveillance from the US National Security Agency and other state-sponsored spies. Now, researchers are renewing their warning that a serious flaw in the way the key exchange is implemented is allowing the NSA to break and eavesdrop on trillions of encrypted connections. . The cost for adversaries is by no means modest. For commonly used 1024-bit keys, it would take about a year and cost a "few hundred million dollars" to crack just one of the extremely large prime numbers that form the starting point of a Diffie-Hellman negotiation. But it turns out that only a few primes are commonly used, putting the price well within the NSA's $11 billion-per-year budget dedicated to "groundbreaking cryptanalytic capabilities." . The cost for adversaries is by no means modest. For commonly used 1024-bit keys, it would take about. years, privacy, advocates, pushed, developers, websites, virtual, private, network. . Dave Wreski
Mar 14, 2017
•
Government
67
security updateperformance improvementOpenSSHOpenSSH 5.7: Key Enhancements In Security And Performance Features
OpenSSH 5.7 has just been released. OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. Read on for a description of the improvements, including Elliptic Curve Cryptography, sftp performance improvements, and much more.. OpenSSH 5.7 has just been released. It will be available from the mirrors listed at https://www.openssh.org/ shortly. OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches, reported bugs, tested snapshots or donated to the project. More information on donations may be found at: https://www.openssh.org/donations.html Changes since OpenSSH 5.6 ======================== Features: * Implement Elliptic Curve Cryptography modes for key exchange (ECDH) and host/user keys (ECDSA) as specified by RFC5656. ECDH and ECDSA offer better performance than plain DH and DSA at the same equivalent symmetric key length, as well as much shorter keys. Only the mandatory sections of RFC5656 are implemented, specifically the three REQUIRED curves nistp256, nistp384 and nistp521 and only ECDH and ECDSA. Point compression (optional in RFC5656) is NOT implemented. Certificate host and user keys using the new ECDSA key types are supported - an ECDSA key may be certified, and an ECDSA key may act as a CA to sign certificates. ECDH in a 256 bit curve field is the preferred key agreement algorithm when both the client and server support it. ECDSA host keys are preferred when learning a host's keys for the first time, or can be learned using ssh-keyscan(1). * sftp(1)/sftp-server(8): add a protocol extension to support a hard link operation. It is available through the "ln" command in the client. The old "ln" behaviour ofcreating a symlink is available using its "-s" option or through the preexisting "symlink" command * scp(1): Add a new -3 option to scp: Copies between two remote hosts are transferred through the local host. Without this option the data is copied directly between the two remote hosts. * ssh(1): automatically order the hostkeys requested by the client based on which hostkeys are already recorded in known_hosts. This avoids hostkey warnings when connecting to servers with new ECDSA keys, since these are now preferred when learning hostkeys for the first time. * ssh(1)/sshd(8): add a new IPQoS option to specify arbitrary TOS/DSCP/QoS values instead of hardcoding lowdelay/throughput. bz#1733 * sftp(1): the sftp client is now significantly faster at performing directory listings, using OpenBSD glob(3) extensions to preserve the results of stat(3) operations performed in the course of its execution rather than performing expensive round trips to fetch them again afterwards. * ssh(1): "atomically" create the listening mux socket by binding it on a temporary name and then linking it into position after listen() has succeeded. This allows the mux clients to determine that the server socket is either ready or stale without races. stale server sockets are now automatically removed. (also fixes bz#1711) * ssh(1)/sshd(8): add a KexAlgorithms knob to the client and server configuration to allow selection of which key exchange methods are used by ssh(1) and sshd(8) and their order of preference. * sftp(1)/scp(1): factor out bandwidth limiting code from scp(1) into a generic bandwidth limiter that can be attached using the atomicio callback mechanism and use it to add a bandwidth limit option to sftp(1). bz#1147 BugFixes: * ssh(1)/ssh-agent(1): honour $TMPDIR for client xauth and ssh-agent temporary directories. bz#1809 * ssh(1): avoid NULL deref on receiving a channel request on an unknown or invalid channel; bz#1842 * sshd(8): remove a debug() that pollutes stderr on client connecting to a server in debug mode; bz#1719 * scp(1): pass through ssh command-line flags and options when doing remote-remote transfers, e.g. to enable agent forwarding which is particularly useful in this case; bz#1837 * sftp-server(8): umask should be parsed as octal * sftp(1): escape '[' in filename tab-completion * ssh(1): Typo in confirmation message. bz#1827 * sshd(8): prevent free() of string in .rodata when overriding AuthorizedKeys in a Match block * sshd(8): Use default shell /bin/sh if $SHELL is "" * ssh(1): kill proxy command on fatal() (we already killed it on clean exit); * ssh(1): install a SIGCHLD handler to reap expiried child process; bz#1812 * Support building against openssl-1.0.0a Portable OpenSSH Bugfixes: * Use mandoc as preferred manpage formatter if it is present, followed by nroff and groff respectively. * sshd(8): Relax permission requirement on btmp logs to allow group read/write * bz#1840: fix warning when configuring --with-ssl-engine * sshd(8): Use correct uid_t/pid_t types instead of int. bz#1817 * sshd(8): bz#1824: Add Solaris Project support. * sshd(8): Check is_selinux_enabled for exact return code since it can apparently return -1 under some conditions. Checksums: ========= - SHA1 (openssh-5.7.tar.gz) = 67cb91772a33fb3a004b39bcdb9148218365494c - SHA1 (openssh-5.7p1.tar.gz) = 423e27475f06e1055847dfff7f61e1ac632b5372 Reporting Bugs: ============== - Please read https://www.openssh.org/report.html Security bugs should be reported directly to
Jan 24, 2011
•
Cryptography
67
security techniqueskey exchangequantum cryptographyNorwegian Researchers Launch Laser Attack on Quantum Key Exchange
Norwegian computer scientists have perfected a laser-based attack against quantum cryptography systems that allows them to eavesdrop on communications without revealing their presence.. One of the biggest commercial uses for quantum cryptography to date has been to securely exchange keys. Unlike traditional key distribution techniques, using quantum mechanics offers a seemingly foolproof upside: any attempt by an attacker to measure quantum data disturbs it -- per the Heisenberg uncertainty principle -- which a quantum cryptography system can detect, thus ensuring that communications remain secure. Enter the laser. The team of researchers from the Norwegian University of Science and Technology (NTNU), the University of Erlangen-N The link for this article located at Information Week is no longer available. . One of the biggest commercial uses for quantum cryptography to date has been to securely exchange ke. norwegian, computer, scientists, perfected, laser-based, attack, against, quantum, cryptography, syste. . LinuxSecurity.com Team
Sep 08, 2010
•
Cryptography
67
quantum encryptionsecure transmissionkey exchange184.6 Km Transmission: Quantum Key Breaks Previous Record
A encrypted quantum key has been transmitted over a distance of 184.6 km, which is 50% further than the previous record of 122 km. The work was done by researchers in the US, based at the Los Alamos National Laboratory (LANL) in New Mexico and the National Institute of Standards and Technology (NIST) in Boulder, Colorado (New Journal of Physics 8 193). The previous record of 122 km was set by researchers at Toshiba . This information is sent in the form of photons and an eavesdropper. This information is sent in the form of photons and an eavesdropper. encrypted, quantum, transmitted, distance, which, further. . LinuxSecurity.com Team
Oct 04, 2006
•
Cryptography
74
cryptographyinternet securitykey exchangeExploring The Impact Of Diffie-Hellman On Internet Transactions Security
In the 1970s, Martin Hellman and Whitfield Diffie wrote the recipe for one of today's most widely used security algorithms in a paper called "New Directions in Cryptography. The paper mapped out the Diffie-Hellman key exchange, a major advancement in Public Key Infrastructure (PKI) technology that allows for secure online transactions and is used in such popular protocols as the Secure Sockets Layer (SSL) and Secure Shell (SSH). In 2000, they received the prestigious Marconi Foundation award for their contributions. . With the world increasingly dependent on the Internet for commerce and a financially-motivated underground of malcode writers working overtime to exploit its weaknesses, there's been plenty of debate over how cryptography must evolve to meet new threats. In this two-part feature, Diffie and Hellman discuss the threats that concern them most and where they think the technology they helped advance is headed. The link for this article located at TechTarget.com is no longer available. . With the world increasingly dependent on the Internet for commerce and a financially-motivated under. 1970s, martin, hellman, whitfield, diffie, wrote, recipe, today's, widely. . Benjamin D. Thomas
Apr 13, 2005
•
Network Security
67
network securitykey exchangesecure communicationExploring Six-Node Quantum Network for Secure Key Exchange
Quantum cryptography has the potential to guarantee perfectly secure communications, but until now all of the prototype systems have been point-to-point links rather than networks that share connections. . . .. Quantum cryptography has the potential to guarantee perfectly secure communications, but until now all of the prototype systems have been point-to-point links rather than networks that share connections. BBN Technologies, Harvard University and Boston University researchers have built a six-node quantum cryptography network that operates continuously to provide a way to exchange secure keys between BBN and Harvard, which is about 10 kilometers away. "Any node in the network can act as a relay," said Chip Elliott, a principal scientist at BBN Technologies. The researchers will soon move one of the network nodes across town to link Boston University into the network, said Elliott. The link for this article located at trnmag.com is no longer available. . Quantum encryption provides unbreakable transmission of data through a novel eight-node system for secure key distribution among organizations.. quantum cryptography, secure communication, key exchange networks. . LinuxSecurity.com Team
Jul 14, 2004
•
Cryptography
67
authenticationencryption techniqueskey exchangeChallenges In Symmetric Cryptography: Trust And Key Exchange
One big issue with using symmetric algorithms is the key exchange problem, which can present a classic catch-22. The other main issue is the problem of trust between two parties that share a secret symmetric key. Problems of trust may be . . . . One big issue with using symmetric algorithms is the key exchange problem, which can present a classic catch-22. The other main issue is the problem of trust between two parties that share a secret symmetric key. Problems of trust may be encountered when encryption is used for authentication and integrity checking. As we saw in Chapter 3, a symmetric key can be used to verify the identity of the other communicating party, but as we will now see, this requires that one party trust the other. . One big issue with using symmetric algorithms is the key exchange problem, which can present a class. using, symmetric, algorithms, exchange, problem, which, present, class. . LinuxSecurity.com Team
Dec 19, 2003
•
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!