Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Required DRAKVUF patch for SNIPER - How to remove this requirement ? #1828

Open
ohault opened this issue Mar 27, 2025 · 2 comments
Open

Required DRAKVUF patch for SNIPER - How to remove this requirement ? #1828

ohault opened this issue Mar 27, 2025 · 2 comments

Comments

@ohault
Copy link

ohault commented Mar 27, 2025

SNIPER is an accurate, robust, and transparent tracing solution for Windows APIs.

SNIPER comes in two implementation variants. One builds on DBI (dynamic binary instrumentation) and another one for CPU virtualization extensions (Intel VT-x) that ships as an extension of the DRAKVUF analysis system, relying on its invisible breakpoints for out-of-guest instrumentation*.

(*) Unfortunately, the SNIPER extension for DRAKVUF relies on a dedicated DRAKVUF patch -
patch-drakvuf-376c03d.diff

According to the roadmap of DRAKVUF, how DRAKVUF design and implementation should be enhanced to enable a future version of SNIPER that will no longer require a dedicated DRAKVUF patch ?

@tklengyel
Copy link
Owner

Patches are always welcome, consider opening a PR and working on upstreaming it

@tklengyel
Copy link
Owner

I looked at the patch briefly and it looks like a good addition. It would still need to be cleaned up and ideally split into multiple PRs but I don't see a blocker for it being upstreamed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants