Advanced Kernel Driver Development
Budget: $1,500 – $3,000 SGD
I have a project that revolves first and foremost around kernel-level driver development. Everything else—server-side logic, secure coding practices, even anti-cheat evasion techniques—supports that single core deliverable: a stable, production-ready Windows kernel driver.
What I need you to build
• A signed, 64-bit Windows driver that hooks seamlessly into the OS at kernel level without triggering modern PatchGuard or DSE protections.
• Clean, well-commented source (C / C++ preferred, WDK toolkit) that follows secure-coding guidelines and is free of common pitfalls such as race conditions, improper IRQL usage, or unchecked user buffers.
• An accompanying user-mode interface (simple CLI is fine) that demonstrates key driver functions and exposes callbacks for future server-side integration.
Why this matters
This driver forms the foundation of a larger product and must therefore be rock-solid, performance-oriented, and security-aware from day one. While my immediate priority is the driver itself, any experience you have with server back-ends or anti-cheat countermeasures will be a plus because the code will later interact with those layers.
Acceptance criteria
1. Driver loads and unloads cleanly on Windows 10/11 x64 with Secure Boot enabled.
2. All requested IOCTLs perform within agreed-upon latency benchmarks.
3. Full source compiles in a fresh WDK/Visual Studio environment without warnings.
4. A concise developer’s guide (markdown or PDF) describes build steps, APIs, and threat-model considerations.
If you’ve previously shipped drivers that passed WHQL or bypassed PatchGuard safely, you are exactly who I’m looking for. Let’s discuss technical details, naming, and signing next.
What I need you to build
• A signed, 64-bit Windows driver that hooks seamlessly into the OS at kernel level without triggering modern PatchGuard or DSE protections.
• Clean, well-commented source (C / C++ preferred, WDK toolkit) that follows secure-coding guidelines and is free of common pitfalls such as race conditions, improper IRQL usage, or unchecked user buffers.
• An accompanying user-mode interface (simple CLI is fine) that demonstrates key driver functions and exposes callbacks for future server-side integration.
Why this matters
This driver forms the foundation of a larger product and must therefore be rock-solid, performance-oriented, and security-aware from day one. While my immediate priority is the driver itself, any experience you have with server back-ends or anti-cheat countermeasures will be a plus because the code will later interact with those layers.
Acceptance criteria
1. Driver loads and unloads cleanly on Windows 10/11 x64 with Secure Boot enabled.
2. All requested IOCTLs perform within agreed-upon latency benchmarks.
3. Full source compiles in a fresh WDK/Visual Studio environment without warnings.
4. A concise developer’s guide (markdown or PDF) describes build steps, APIs, and threat-model considerations.
If you’ve previously shipped drivers that passed WHQL or bypassed PatchGuard safely, you are exactly who I’m looking for. Let’s discuss technical details, naming, and signing next.