<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Unsigned on fahersto&#39;s blog</title>
    <link>https://blog.lentic.de/tags/unsigned/</link>
    <description>Recent content in Unsigned 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>Fri, 18 Mar 2022 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.lentic.de/tags/unsigned/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Register handle operation callbacks from unsigned drivers with this one weird trick</title>
      <link>https://blog.lentic.de/posts/obregistercallbacks/</link>
      <pubDate>Fri, 18 Mar 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.lentic.de/posts/obregistercallbacks/</guid>
      <description>Monitor handle acquisition Acquiring a handle to a target process is a critical step in many code injection techniques. The Windows operating system exposes a mechanism that allows kernel mode drivers to supply handle operation callbacks. These callbacks can be registered by calling ObRegisterCallbacks. When a handle is created or duplicated the pre-operation callback is invoked before the operation is performed and the post-operation callback after the operation occurred. This mechanism is utilized by many antivirus and Anti-Cheat solutions to protect processes from code injection.</description>
    </item>
  </channel>
</rss>
