<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: feearent</title><link>https://news.ycombinator.com/user?id=feearent</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 07 Nov 2026 18:25:47 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=feearent" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by feearent in "Alpine Linux Security Advisory: OpenSSH-server password authentication bypass"]]></title><description><![CDATA[
<p>Thank you for your comment, it's very refreshing (and comforting for me actually). Have a good day.</p>
]]></description><pubDate>Thu, 05 Nov 2026 20:16:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=50383907</link><dc:creator>feearent</dc:creator><comments>https://news.ycombinator.com/item?id=50383907</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50383907</guid></item><item><title><![CDATA[New comment by feearent in "Show HN: HackerTV – HN's most-recommended Youtube videos as 24/7 TV channels"]]></title><description><![CDATA[
<p>I think it's the future for prompt-based engineering honestly. I employ it myself too. I Keep a prompts file, either for sharing or looking back at it. I think Open Source Software should adopt it in their repos for a. transparency and b. learning material for the future.</p>
]]></description><pubDate>Thu, 05 Nov 2026 19:46:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=50383528</link><dc:creator>feearent</dc:creator><comments>https://news.ycombinator.com/item?id=50383528</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50383528</guid></item><item><title><![CDATA[New comment by feearent in "OpenSSH 10.6p2 has been released with a workaround for a critical vulnerability"]]></title><description><![CDATA[
<p>Not really related to the topic, but AI-popular sentences and language structure stand out to people right away these days right? I noticed some.<p>"If you cannot update yet, at least disable password logins: set PasswordAuthentication no in your sshd configuration and restart sshd. <i>Either one closes the hole.</i>" (only AI would characterize a critical SSH implementation vulnerability as a hole closing game)<p>An attacker who can reach your SSH port can log in without knowing any password. <i>It takes one connection, works every time, and needs no retries.</i> (It sounds like the writer is bragging about the exploit instead of describing it. AI does this)<p>The attacker needs the name of an account whose password field is * (an account with no password set, which is normal for key-only accounts), and needs the machine to have at least one other account with a $5$ or $6$ password hash. The attacker then sends a very long password (257 to 1024 bytes). <i>One user with a password is enough: it makes every account without one reachable.</i> (same as above made stronger with the 'statement: statement2' format)<p>"Users coming from a directory service through musl-nscd (nslcd, winbind, sssd), <i>since they have no shadow entry.</i>" (a human would be more clear about what a shadow entry is and give more context, I think)<p>Hmm the rest of the article (the remaining 70-80%) seems quite human.<p>Anyway, not sure why I spent 10+ minutes on this. It just jumps at me right away.</p>
]]></description><pubDate>Thu, 05 Nov 2026 19:02:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=50382986</link><dc:creator>feearent</dc:creator><comments>https://news.ycombinator.com/item?id=50382986</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50382986</guid></item></channel></rss>