<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ssh-Security on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/ssh-security/</link><description>Recent content in Ssh-Security on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 28 May 2026 15:57:49 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/ssh-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Honeypots Set the Trap Watch the Attackers and Know When You Are Standing in One</title><link>https://hackingpassion.com/honeypot-ethical-hacking/</link><pubDate>Thu, 28 May 2026 15:57:49 +0200</pubDate><guid>https://hackingpassion.com/honeypot-ethical-hacking/</guid><description>&lt;h1 id="honeypots-set-the-trap-watch-the-attackers-and-know-when-you-are-standing-in-one">Honeypots: Set the Trap, Watch the Attackers, and Know When You Are Standing in One&lt;/h1>
&lt;p>Put a server on the internet with port 22 open and the first login attempt arrives within minutes, not days. Automated scanners sweep through IPv4 addresses around the clock, and anything with an open port gets added to a target list almost immediately. A honeypot is built to be found exactly like this, because getting found is the point. This post covers what honeypots actually are, what attackers do in the first thirty seconds after getting in, how to set one up and test it, how to recognize one during a pentest, and the advanced setups for when things get serious.&lt;/p></description></item><item><title>PamDOORa Steals SSH Credentials on Linux by Hiding Inside PAM Where No Antivirus Looks</title><link>https://hackingpassion.com/pamdoora-linux-ssh-backdoor/</link><pubDate>Sun, 10 May 2026 12:12:16 +0200</pubDate><guid>https://hackingpassion.com/pamdoora-linux-ssh-backdoor/</guid><description>&lt;p>A backdoor called &lt;strong>PamDOORa&lt;/strong> targets Linux systems through PAM and steals SSH credentials from every user who logs in. It leaves no trace in process lists, antivirus, or logs. When the security team connects via SSH to investigate, their credentials get stolen too.&lt;/p>
&lt;p>When someone logs into a Linux server, the system runs &lt;strong>PAM&lt;/strong> to check the password. PAM stands for &lt;strong>Pluggable Authentication Modules&lt;/strong>, and it handles authentication for everything that requires a login: SSH, sudo, the login prompt. Instead of building that check into each program separately, Linux sends everything through PAM using configuration files stored in &lt;code>/etc/pam.d/&lt;/code>, one file per service. The file for SSH is &lt;code>/etc/pam.d/sshd&lt;/code>. It tells PAM which modules to run, in what order, and what to do when one fails.&lt;/p></description></item></channel></rss>