<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reverse-Engineering on soyuka.me</title><link>https://soyuka.me/tags/reverse-engineering/</link><description>Recent content in Reverse-Engineering on soyuka.me</description><generator>Hugo</generator><language>en-us</language><copyright>All rights reserved - 2026</copyright><lastBuildDate>Wed, 21 Oct 2026 13:01:06 +0200</lastBuildDate><atom:link href="https://soyuka.me/tags/reverse-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Reverse Engineering an Undocumented Binary Format to SQL</title><link>https://soyuka.me/reverse-engineering-a-binary-format-to-sql/</link><pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate><guid>https://soyuka.me/reverse-engineering-a-binary-format-to-sql/</guid><description>&lt;p&gt;I recently had to get data out of an old piece of software from 2020 whose files looked unreadable: a few hundred binary files, no documentation, and I wanted to query them with SQL. This post is about the method, how to find the containers, the record layouts and the links between files from the data alone, and how to check you&amp;rsquo;re not fooling yourself along the way.&lt;/p&gt;</description></item></channel></rss>