<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Openssh on Kuldeep Pisda</title><link>https://kdpisda.in/tag/openssh/</link><description>Recent content in Openssh on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 07 Nov 2026 08:30:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/openssh/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenSSH Accepted a 300-Byte Password for Accounts With No Password. The Bug Is in musl and Alpine's Shadow File</title><link>https://kdpisda.in/openssh-10-6p2-musl-crypt-star-oversized-password-bypass/</link><pubDate>Sat, 07 Nov 2026 08:30:00 +0530</pubDate><guid>https://kdpisda.in/openssh-10-6p2-musl-crypt-star-oversized-password-bypass/</guid><description>&lt;p&gt;A password of 257 to 1024 bytes will log in to any account whose &lt;code&gt;/etc/shadow&lt;/code&gt; field is &lt;code&gt;*&lt;/code&gt;, on an sshd that is linked against musl and runs without PAM. That is CVE-2026-123158, nicknamed &amp;ldquo;sshole&amp;rdquo; by its reporter, Özgün Kültekin of Wakefield. OpenSSH shipped 10.6p2 on November 5 with a workaround, and Alpine published fixed packages for every branch from 3.16 to edge the same day.&lt;/p&gt;
&lt;p&gt;The interesting part is that no single component is wrong in isolation. Two decisions made years apart agree on one character.&lt;/p&gt;</description></item></channel></rss>