Did a new release of `ssh-tpm-agent`, `v0.8.0`.

Notable changes is hierarchy keys, keyctl backed passwords and some preliminary landlock support.

https://github.com/Foxboron/ssh-tpm-agent/releases/tag/v0.8.0

Der @leyrer ist einer meiner persönlichen Helden. Er erklärt immer sehr unterhaltsam Themen rund um SSH, Kommandozeile und Co. die man auch wirklich gut bei der Arbeit anwenden kann und das Leben häufig leichter machen.

Liebe geht raus für seinen Einsatz.

Leider habe ich bisher nie live die Ehre gehabt, aber es ist ja noch nicht aller Tage Abend und ich hoffe er macht noch einige Talks.

Überzeugt euch selbst:
https://media.ccc.de/search?p=Der+Leyrer

A few words on SSH public keys read from AuthorizedKeysFile(s) and obtained programmatically from OpenSSH's AuthorizedKeysCommand program.

https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/

What do you use to manage the contents of ~/.ssh/authorized_keys?
Roughly, in how many distinct remote locations do you manage that file?
Do they generally contain the same set of keys, or is there some variation? #ssh #OpenSSH #SysAdmin #DevOps

Mi máquina virtual estándar sobre @proxmox es definitivamente @alpinelinux
Imagen virtual: x86_64

Configuración minimalista:

#OpenSSH en puerto alternativo:

port 8765

AllowUsers user1

PermitRootLogin no

Usuario con permisos doas:

/etc/doas.conf → permit persist alpine as root

Cortafuegos:

#UFW con reglas estrictas

Control de accesos:

#Fail2Ban notificando por #ntfy cada ban

Todo en 138 MB, súper eficiente y sin paquetes innecesarios.

Suppose you have `AllowUsers foo` set in sshd_config. Normally, this will result in logs like:

[date] [host] sshd-session[pid]: Invalid user ubuntu from 195.178.110.18 port 44128

But sometimes, you see this instead:

[date] [host] sshd-session[pid]: error: PAM: Authentication error for illegal user centos from 82.193.122.91

What are the circumstances in which the attacker is able to get through sshd to interact with the PAM stack despite having given a non-permitted login? #infosec #openssh

#openssh with #yubikey
On the computer, I have only a pubkey, no privkey:

❯ ls ~/.ssh/rainer-yubikey-1*
/Users/rainer/.ssh/rainer-yubikey-1.pub

❯ ssh halde
Confirm user presence for key ED25519-SK SHA256:ug3mPO6C+LCYvj6FMG5HE02B5MSJw74a0sLKxooaqJY
Enter PIN for ED25519-SK key /Users/rainer/.ssh/rainer-yubikey-1:
Confirm user presence for key ED25519-SK SHA256:ug3mPO6C+LCYvj6FMG5HE02B5MSJw74a0sLKxooaqJY
User presence confirmed

The programs included with the Debian GNU/Linux system are free software;

youtube.com/watch?v=gFrd3WiOcP…

Kudos to @bkoehn
KC and The Sunshine Band - That's The Way (I Like It) 1977 (Remastered)

#Windows -Vorschau: #OpenSSH-Korrekturen, #Recall-Neustart, farbiges Akkusymbol | heise online https://www.heise.de/news/Windows-Vorschau-OpenSSH-Korrekturen-Recall-Neustart-farbiges-Akkusymbol-10293388.html #Microsoft

Microsoft's KB5052077 Update: A Critical Fix for SSH Connectivity on Windows 10

In a recent move to enhance user experience, Microsoft has released the KB5052077 cumulative update for Windows 10, addressing a significant SSH connectivity issue. This update not only resolves the l...

https://news.lavx.hu/article/microsoft-s-kb5052077-update-a-critical-fix-for-ssh-connectivity-on-windows-10

Latest issue of my curated #cybersecurity and #infosec list of resources for week #08/2025 is out!

It includes the following and much more:

➝ Two Vulnerabilities in #OpenSSH
➝ #Russia Increasingly Using #AI in Cyber Espionage
➝ South Korea Blocking Downloads of #DeepSeek
➝ Palo Alto Networks & Juniper Networks Flaws Being Exploited
➝ #Apple to Remove E2E #Encryption in the UK;

Subscribe to the #infosecMASHUP newsletter to have it piping hot in your inbox every week-end

https://infosec-mashup.santolaria.net/p/infosec-mashup-082025?r=299go8&utm_campaign=post&utm_medium=web&showWelcomeOnShare=false

New OpenSSH vulnerabilities alert! Hackers could exploit recent flaws for man-in-the-middle & DoS attacks—time to act! Secure your servers now with these essential fixes to protect sensitive data. #OpenSSH #CyberSecurity #TechTips #SysAdmin

https://pupuweb.com/how-to-protect-against-new-openssh-threats/

Sicherheitsupdate #OpenSSH: Angreifer können sich in Verbindungen einklinken | Security https://www.heise.de/news/Sicherheitsupdate-OpenSSH-Angreifer-koennen-sich-in-Verbindungen-einklinken-10287547.html #Patchday

Does anyone know if VerifyHostKeyDNS in OpenSSH does DNSSEC validation?

Or what a secure fingerprint or insecure finger print mean in ssh_config? (Maybe md5 vs sha256?)

Help us test patches for the #OpenSSH vulnerability CVE-2025-26465, and see the current status of those patches: https://almalinux.org/blog/2025-02-20-test-patches-for-cve-2025-26465/ #linux #security

Bitte sorgt dafür, dass Euer OpenSSH aktualisiert wird. Die Version v9.9_p2-r0 behebt zwei schwerwiegende Sicherheitslücken.

Wenn ihr home assistant mit SSH Addon betreibt, macht bitte ein Update. Die aktuelle Version enthält ein Update von OpenSSH auf v9.9_p2-r0 das zwei schwerwiegende Sicherheitslücken schließt.

Thanks to #OpenSSH I just had to update 4 notebooks and 4 thin clients!

.oO(NO, me being a hardware hoarding^Wcollecting nerd has nothing to do with that!)

New #OpenSSH flaws expose #SSH servers to #MiTM and DoS attacks

https://www.bleepingcomputer.com/news/security/new-openssh-flaws-expose-ssh-servers-to-mitm-and-dos-attacks/

New, critical OpenSSH vulnerabilities expose SSH servers to MitM and DoS Attacks. OpenSSH, one of the most widely used tools in the world, has two new vulnerabilities that could leave your systems vulnerable to man-in-the-middle (MitM) and denial-of-service (DoS) attacks.

What You Should Do:
Update to OpenSSH 9.9p2 immediately.
Disable VerifyHostKeyDNS unless absolutely necessary.
Enforce connection rate limits and monitor SSH traffic for anomalies.

Read the details: https://www.bleepingcomputer.com/news/security/new-openssh-flaws-expose-ssh-servers-to-mitm-and-dos-attacks/