<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>VEH on fahersto&#39;s blog</title>
    <link>https://blog.lentic.de/tags/veh/</link>
    <description>Recent content in VEH on fahersto&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>&lt;a href=&#34;https://creativecommons.org/licenses/by-nc/4.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CC BY-NC 4.0&lt;/a&gt;</copyright>
    <lastBuildDate>Wed, 15 Sep 2021 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.lentic.de/tags/veh/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>hookFTW - hook for the win(dows)</title>
      <link>https://blog.lentic.de/posts/hookftw/</link>
      <pubDate>Wed, 15 Sep 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.lentic.de/posts/hookftw/</guid>
      <description>This is a post is about my C++ hooking library for Windows (GitHub).&#xA;What is a hooking library? A hooking library allows to change a target programs control flow. This can be useful to debug own applications but also to change or extend functionality of other programs. This functionality can be achieved using different methods. I implemented the following methods:&#xA;Byte patching .text section Import Address Table (IAT) Virtual Function Table (VFT) Vectored Expcetion Handler (VEH) Why write another Windows hooking library?</description>
    </item>
  </channel>
</rss>
