<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home on /home/tira</title><link>https://asabbag.com/</link><description>Recent content in Home on /home/tira</description><generator>Hugo</generator><language>en</language><copyright>2025-2027 © A:S</copyright><lastBuildDate>Mon, 27 Oct 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://asabbag.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Creating and Accessing ELF sections, in userland and beyond</title><link>https://asabbag.com/posts/creating_and_accessing_elf_sections/</link><pubDate>Mon, 27 Oct 2025 00:00:00 +0000</pubDate><guid>https://asabbag.com/posts/creating_and_accessing_elf_sections/</guid><description>&lt;h1 id="userland-land-of-the-free"&gt;Userland: Land of the Free&lt;/h1&gt;&#10;&lt;p&gt;Everything starts with a simple a.out. We will now demonstrate how to create and place variables into custom sections using GCC and Clang attributes, as well as accessing these sections using obscure linker features.&lt;/p&gt;&#10;&lt;h2 id="creation"&gt;Creation&lt;/h2&gt;&#10;&lt;p&gt;One very useful but not widely known GCC and Clang attribute is &lt;code&gt;section&lt;/code&gt;, which allows the programmer to determine in which section a variable is placed. Normally, the compiler decides which variables go to which section in an object file (.o), and the linker combines all the object files that you provide it with, and merges the sections in the final ELF.&lt;/p&gt;</description></item><item><title>Flashing OpenWRT on a Cudy WR3000E</title><link>https://asabbag.com/posts/flashing_openwrt_on_cudy_wr3000e/</link><pubDate>Wed, 16 Jul 2025 00:00:00 +0000</pubDate><guid>https://asabbag.com/posts/flashing_openwrt_on_cudy_wr3000e/</guid><description>&lt;p&gt;I was recently looking for a router to buy, my primary concerns being OpenWRT support, good amounts of ROM and RAM, and a not so expensive price. I came across the Cudy WR3000 series, and I decided to go for the Cudy WR3000E on &lt;a href="https://www.amazon.fr/dp/B0DMNXXNTG"&gt;Amazon&lt;/a&gt;. The router has 128MB of ROM, plenty of space for any packages or configuration one can make, and 256MB RAM, which is enough for my use case. You can see the full specification on the &lt;a href="https://www.cudy.com/fr-fr/products/wr3000e-1-0"&gt;Cudy website&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>About me</title><link>https://asabbag.com/about/</link><pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate><guid>https://asabbag.com/about/</guid><description>&lt;p&gt;Hello, I&amp;rsquo;m Amir, a.k.a tira. My interests lie in systems programming, compilers, computer architecture, and virtualization security. I particularly like the interaction between software and hardware, and unraveling the layers of abstraction upon which our worldview is built on.&lt;/p&gt;&#10;&lt;p&gt;In 2026, I worked with the Benagil team at Télécom SudParis on &lt;a href="https://asabbag.com/projects/#intel-cet-in-x86-64-hypervisors"&gt;Intel CET in x86-64 hypervisors&lt;/a&gt;. I implemented control-flow protections and investigated the interaction between interrupt delivery and supervisor shadow stacks.&lt;/p&gt;</description></item><item><title>Archive</title><link>https://asabbag.com/archives/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://asabbag.com/archives/</guid><description>archives</description></item><item><title>Projects</title><link>https://asabbag.com/projects/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://asabbag.com/projects/</guid><description>&lt;h2 id="intel-cet-in-x86-64-hypervisors"&gt;Intel CET in x86-64 Hypervisors&lt;/h2&gt;&#10;&lt;p&gt;&lt;em&gt;Research · École Polytechnique · Télécom SudParis · 2026&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;I worked with the Benagil team at Télécom SudParis to investigate Intel Control-flow Enforcement Technology (CET) in hypervisor environments. My focus was on how its protections interact with virtualization and interrupt handling.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Implemented host-level Indirect Branch Tracking and Supervisor Shadow Stacks in a research hypervisor.&lt;/li&gt;&#10;&lt;li&gt;Investigated the difficulties of Linux supervisor shadow stacks with legacy interrupt delivery, particularly nested NMIs and interrupt returns.&lt;/li&gt;&#10;&lt;li&gt;Evaluated a hypervisor-assisted design for guest supervisor shadow stacks.&lt;/li&gt;&#10;&lt;li&gt;Learned about the new FRED event delivery architecture.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="kohnard"&gt;&lt;a href="https://github.com/Amir1453/kohnard"&gt;kohnard&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;&lt;em&gt;Rust · x86-64&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>