<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>SL3000 on +5 Security Research</title><link>https://overkazaf.github.io/blogs/tags/sl3000/</link><description>Recent content in SL3000 on +5 Security Research</description><generator>Hugo</generator><language>zh-cn</language><lastBuildDate>Mon, 24 Aug 2026 14:00:00 +0800</lastBuildDate><atom:link href="https://overkazaf.github.io/blogs/tags/sl3000/index.xml" rel="self" type="application/rss+xml"/><item><title>一段 UTF-16 XML 凭什么管住 4K？PlayReady 的套娃式架构</title><link>https://overkazaf.github.io/blogs/posts/playready-pro-license-sl3000-deep-dive/</link><pubDate>Mon, 24 Aug 2026 14:00:00 +0800</pubDate><guid>https://overkazaf.github.io/blogs/posts/playready-pro-license-sl3000-deep-dive/</guid><description>从 DASH 里的 PlayReady SystemID 开始，逐字节拆开 PSSH、PRO 与 WRMHEADER，再沿 License、设备证书、SL2000/SL3000、TEE 和 OPL 还原 PlayReady 的完整信任链，并给出可复现的自有内容实验与参考项目地图。</description></item></channel></rss>