<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Openwrt on binreaper</title>
    <link>https://binreaper.pages.dev/tags/openwrt/</link>
    <description>Recent content in Openwrt on binreaper</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://binreaper.pages.dev/tags/openwrt/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cracking Passwords from Embedded Linux Devices: The musl DES Crypt $ Salt Problem</title>
      <link>https://binreaper.pages.dev/posts/2026-03-04-musl-des-crypt-salt/</link>
      <pubDate>Wed, 04 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://binreaper.pages.dev/posts/2026-03-04-musl-des-crypt-salt/</guid>
      <description>&lt;p&gt;When extracting &lt;code&gt;/etc/shadow&lt;/code&gt; from embedded Linux devices — routers, IoT gateways, cameras — you&amp;rsquo;ll occasionally encounter password hashes that every standard cracking tool refuses to touch. Not because the hash is strong, but because the C library that generated it plays by slightly different rules.&lt;/p&gt;&#xA;&lt;p&gt;This post documents a specific case: DES crypt hashes with a &lt;code&gt;$&lt;/code&gt; character in the salt, generated by musl libc on an OpenWrt-based router. The fix is a one-character substitution that makes the hash crackable in seconds.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
