<?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 Taha Draidia</title><link>https://tahadraidia.com/tags/reverse-engineering/</link><description>Recent content in reverse-engineering on Taha Draidia</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 14 Jul 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://tahadraidia.com/tags/reverse-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Expanding Our WinDBG Arsenal - Handleex Extension</title><link>https://tahadraidia.com/posts/expanding-our-windbg-arsenal-handleex-extension/</link><pubDate>Fri, 14 Jul 2023 00:00:00 +0000</pubDate><guid>https://tahadraidia.com/posts/expanding-our-windbg-arsenal-handleex-extension/</guid><description>This post has been ported from Darkwaves InfoSec blog.
Introduction When it comes to dynamic analysis on Windows, WinDBG is our option of choice. The debugger provides several built-in extensions such as analyze, heap, gle and allows extendibility by creating extensions using several programming languages.
During an engagement for a client, a need emerged to retrieve the filename associated with a file handle, all that is within the userland.</description></item></channel></rss>