
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Sun, 09 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/x86/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/security/2026-08-09-what-a-hardware-backdoor-actually-is.en</guid>
    <title>The Exact Scope of the Phrase x86 Hardware Backdoor — Reading rosenbridge as Its Author Wrote It</title>
    <link>https://www.youngju.dev/blog/security/2026-08-09-what-a-hardware-backdoor-actually-is.en</link>
    <description>The repository title says hardware backdoors in x86 CPUs, but the body of the README states that the only thing believed to be affected is the VIA C3 and that later generations no longer carry the feature. In the disclaimer the author writes that this appears to be a feature built in good faith for the embedded market that was unintentionally left enabled in some early generations, and states explicitly that no malice is implied. This post carries that boundary over exactly, then turns to what actually generalizes here, which is the method rather than the finding: the sandsifter approach of systematically sweeping the entire x86 instruction space to find undocumented instructions, and what such a scan really turns up.</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>security</category><category>hardware</category><category>x86</category><category>cpu</category><category>fuzzing</category><category>reverse-engineering</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/security/2026-08-09-what-a-hardware-backdoor-actually-is.ja</guid>
    <title>x86ハードウェアバックドアという言葉の正確な範囲 — rosenbridgeを著者が書いたとおりに読む</title>
    <link>https://www.youngju.dev/blog/security/2026-08-09-what-a-hardware-backdoor-actually-is.ja</link>
    <description>リポジトリの題名はx86 CPUのハードウェアバックドアとなっていますが、READMEの本文は、影響を受けるのはVIA C3だけと考えられており以後の世代にはこの機能がないと明示します。著者は免責条項で、これは組み込み市場向けの機能として善意で作られ、初期の一部世代で意図せず有効なまま残ったものと見ていると述べ、悪意を含意しないと書いています。この記事はその境界線を正確に移したうえで、実際に一般化されるのは発見ではなく方法であるという点を扱います。文書化されていない命令を探すためにx86の命令空間全体を体系的に走査するsandsifterのアプローチと、そのスキャンが実際に何を見つけるのかを整理します。</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>security</category><category>hardware</category><category>x86</category><category>cpu</category><category>fuzzing</category><category>reverse-engineering</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/security/2026-08-09-what-a-hardware-backdoor-actually-is</guid>
    <title>x86 하드웨어 백도어라는 말의 정확한 범위 — rosenbridge를 저자가 쓴 대로 읽기</title>
    <link>https://www.youngju.dev/blog/security/2026-08-09-what-a-hardware-backdoor-actually-is</link>
    <description>저장소 제목은 x86 CPU의 하드웨어 백도어라고 되어 있지만, README 본문은 영향받는 것이 VIA C3뿐인 것으로 여겨지며 이후 세대에는 이 기능이 없다고 명시합니다. 저자는 면책 조항에서 이것이 임베디드 시장용 기능으로 선의로 만들어졌다가 초기 세대에서 의도치 않게 활성화된 채 남은 것으로 본다며 악의를 함의하지 않는다고 적었습니다. 이 글은 그 경계선을 정확히 옮긴 뒤, 정작 일반화되는 것은 발견이 아니라 방법이라는 점을 다룹니다. 문서화되지 않은 명령어를 찾기 위해 x86 명령어 공간 전체를 체계적으로 훑는 sandsifter의 접근과, 그 스캔이 실제로 무엇을 찾아내는지 정리합니다.</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>security</category><category>hardware</category><category>x86</category><category>cpu</category><category>fuzzing</category><category>reverse-engineering</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/security/2026-08-09-what-a-hardware-backdoor-actually-is.zh</guid>
    <title>「x86 硬件后门」这句话的准确范围 —— 按作者写下的样子来读 rosenbridge</title>
    <link>https://www.youngju.dev/blog/security/2026-08-09-what-a-hardware-backdoor-actually-is.zh</link>
    <description>仓库标题写的是 x86 CPU 的硬件后门，但 README 正文明确写着：受影响的被认为只有 VIA C3，而此后的世代已经不再具备这项功能。作者在免责声明里写道，他认为这是为嵌入式市场出于善意做出来的一项有用功能，只是在早期若干世代里被无意间保留成了启用状态，并明言这不含任何恶意的意味。本文先把这条边界线准确地搬过来，再讨论真正被一般化的其实不是这个发现，而是方法：sandsifter 为寻找未文档化指令而系统性扫描整个 x86 指令空间的思路，以及这种扫描实际会找出些什么。</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>security</category><category>hardware</category><category>x86</category><category>cpu</category><category>fuzzing</category><category>reverse-engineering</category>
  </item>

    </channel>
  </rss>
